Loading ToolBench
A Spring Boot-based MCP server that provides weather information tools
Single tool with minimal definition quality. Tool name 'getWeather' violates verb_noun convention (should be 'get_weather'). Description is present but generic (23 chars, below 34-char p10 baseline). No output schema documented. No error handling guidance. Tool implementation returns hardcoded string 'harish' instead of actual weather data, indicating incomplete/placeholder implementation.
Get weather information by city name
Tool name violates verb_noun convention: 'getWeather' should be 'get_weather'. Camel case breaks LLM parsing of intent from name alone.
Parameter 'cityName' lacks description. Rubric requires every parameter to have a non-empty description explaining what it controls. LLMs cannot infer meaning from names alone.
No output schema documented. Tool returns unstructured string 'harish' instead of structured weather data (temperature, condition, humidity, etc.). LLMs cannot plan downstream calls or extract relevant fields.
Tool description is 23 characters ('Get weather information by city name'), below the p10 baseline of 34 chars. Lacks context for when/why to use it vs alternatives, and does not state what the tool returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
No error handling or recovery guidance. Tool will fail silently or return invalid data for unknown cities. No guidance for LLM on what to do next (retry, ask user, try alternative).