Loading ToolBench
MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers, demonstrating remote MCP authentication and authorization flows
Single tool 'add' has critical definition gaps. Input schema present with Zod types (a, b as numbers) but parameter descriptions are null, violates the requirement that every parameter needs a description. Tool description is missing entirely (no docstring visible in registration). Output schema not documented. No error handling guidance. Naming is generic and doesn't follow verb_noun convention (should be 'sum_numbers' or 'calculate_sum'). This server fails multiple hard scoring rules.
Tool 'add' has no description. LLMs cannot determine when or why to select this tool without a docstring explaining its purpose, inputs, and outputs.
All input parameters (a, b) have null descriptions. Parameter descriptions are mandatory, LLMs cannot infer that 'a' and 'b' are operands for addition without explicit text.
Output schema is not documented. The tool returns text content but LLMs need to know the exact response structure (e.g., is it a number string, formatted result, error message?).
Tool name 'add' is generic and does not follow verb_noun convention. Should be 'sum_numbers', 'calculate_sum', or 'add_numbers' to clarify the action and operands.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | 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.