Loading ToolBench
MCP server with OAuth 2.0 authorization provider running on Cloudflare Workers
Single tool 'add' has critical definition gaps. Tool description is missing entirely (null in schema). No output schema documented. No error handling guidance. Naming is generic ('add') without context of what domain this serves. This server appears to be a minimal demo/template rather than production-grade tooling.
Tool 'add' has no description. LLMs cannot determine when or why to select this tool without a description explaining its purpose, domain, and use case.
Input parameters 'a' and 'b' have null descriptions. LLMs cannot infer that 'a' and 'b' are operands for addition without explicit descriptions.
No output schema documented. Tool returns {content: [{type: 'text', text: string}]} but this structure is not declared in the tool definition. LLMs cannot plan downstream calls or extract results reliably.
Tool name 'add' is generic and lacks domain context. Does it add numbers, items to a list, users to a group, or something else? Ambiguous naming forces LLMs to guess.
| 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.