Loading ToolBench
Model Context Protocol (MCP) server for X Y Z
Single tool 'add_two_numbers' has critical definition gaps. Tool name lacks action verb clarity (should be 'sum_numbers' or 'calculate_sum'). Description is minimal (14 chars, below 20-char threshold). Input parameters 'a' and 'b' have null descriptions, violates requirement that every parameter must have a non-empty description. No output schema documented. No error handling guidance. Tool is trivial (arithmetic) and does not reflect real-world MCP use cases, but evaluated on its own merits, it fails basic quality standards.
Add two numbers
Parameter descriptions are null. Both 'a' and 'b' parameters lack descriptions, violating the requirement that every parameter must have a non-empty description explaining what it controls.
Tool description is 14 characters ('Add two numbers'), below the 20-character minimum. LLM cannot determine when or why to select this tool.
Tool name 'add_two_numbers' does not start with a clear action verb. Should be 'sum_numbers', 'calculate_sum', or 'add_numbers' to match verb_noun convention and help LLMs parse intent from the name alone.
No output schema documented. LLMs cannot plan downstream calls or extract data without knowing what fields to expect. Tool returns text content but structure is not formally declared.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If inputs are invalid (non-numeric, NaN, Infinity), the tool provides no actionable error message to guide the LLM's next step.