Loading ToolBench
A local MCP server providing utility tools for string operations and UUID generation
Two simple tools with minimal descriptions and incomplete parameter documentation. Both tools have valid JSON Schema input definitions with required fields and type constraints, but descriptions are extremely brief (10-13 chars, well below the 34-char p10 baseline). Parameter descriptions are missing entirely, 'input' and 'count' lack explanations of their purpose, constraints, or expected ranges. No output schema documentation. No error handling guidance. No tool annotations. The tools are read-only and trivial, but the definitions lack the rigor needed for production agent use.
Generate a specified number of UUIDs
Get the length of a string
Parameter descriptions completely missing. 'input' and 'count' parameters have no descriptions explaining their purpose, constraints, or expected ranges. LLMs cannot infer parameter semantics from names alone.
Tool descriptions are extremely brief (10-13 characters, far below 34-char p10 baseline). 'Get the length of a string' and 'Generate a specified number of UUIDs' lack context for when to use each tool, what they return, or any prerequisites.
No output schema documentation. Tool handlers return Content[] with text fields, but the response structure is not formally documented. LLMs cannot plan downstream operations without knowing the output shape.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
No numeric constraints on 'count' parameter. generateUUIDs accepts any number without bounds, LLMs could pass 1000000, causing memory exhaustion or timeout. Should specify min/max (e.g., 1-1000).
No error recovery guidance. Handler returns generic 'Invalid input' on validation failure. LLMs receive no actionable next steps, should specify what constraint was violated and how to fix it.