Loading ToolBench
Single tool with critical definition gaps. Tool name 'getWeatherDataByCityName' uses camelCase (non-standard for MCP) and lacks clarity on action. Input schema present but parameter 'city' has null description (violates pattern:tool-description). No tool description visible in registration. Output schema undocumented, response structure inferred from implementation only. Error handling returns generic 'Unable to fetch data' with no recovery guidance. Hardcoded city data (Karachi, Quetta) suggests mock implementation unsuitable for production.
Tool parameter 'city' has null description, violates pattern:tool-description requirement that every parameter must have a non-empty description explaining what it controls.
Tool registration lacks description, LLMs cannot determine when or why to select this tool without a non-empty description (10 - 1024 chars recommended).
Output schema undocumented, response structure (temp, forecast, error fields) is inferred from implementation only. LLMs need explicit schema documentation to plan downstream calls and extract data reliably.
Error handling returns generic 'Unable to fetch data' with no recovery guidance, violates pattern:recovery-guide. Should indicate whether error is retryable, user-fixable, or fatal, and suggest next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
Tool name uses camelCase (getWeatherDataByCityName) instead of snake_case verb_noun convention (get_weather_by_city_name). Non-standard naming reduces LLM parsing clarity.