Loading ToolBench
MCP server that provides developer information lookup by name
Single tool 'getDeveloperInfoByName' has critical definition gaps. Parameter 'name' has null description (violates pattern:tool-description). Input schema uses Zod validation but lacks proper JSON Schema documentation in the tool registration. No output schema is documented. Error handling returns unstructured text ('Developer not found', error.message) without recovery guidance. Tool does one thing (lookup) but lacks the LLM-optimized descriptions required for reliable agent selection.
Tool has no description. LLMs cannot determine when to select this tool without explicit guidance on purpose and use case.
Parameter 'name' has null description. LLMs cannot infer what format or values are expected (e.g., first name only, full name, case-sensitive?).
No output schema documented. LLMs do not know what fields to expect in the response or how to chain this tool with others.
Error handling returns unstructured text without recovery guidance. 'Developer not found' does not tell the LLM what to do next (e.g., try a partial name search).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
Input schema uses Zod validation but does not expose a formal JSON Schema to the MCP protocol. The refine() call is implementation detail, not schema documentation.