MCP server that provides current weather information for specified cities using the OpenWeatherMap API
Single tool with critical gaps. Tool name is acceptable (verb + noun pattern), but descriptions are minimal, parameters lack depth, and output schema is undocumented. Error handling exists but is not actionable. No input validation beyond API-level constraints. The server exposes a READ_ONLY operation but lacks documentation of what users should do in error cases. Per-tool scoring: get_weather scores 42/100 overall.
Returns the current weather information for the specified city.
Tool description is 81 characters, below the baseline of 194 chars average for A+ tools. It states WHAT but omits WHEN to use it and what happens on failure. LLMs cannot determine when to select this tool over alternatives or what to do if the API fails.
Parameter 'lang' lacks meaningful description. The description 'The language code for the weather description' does not state valid values, format, or examples. An LLM has no guidance on what to pass, 'en', 'en-US', 'english'? This violates the 'every parameter needs a description explaining what it controls' rule.
Output schema is not documented. The code returns a dict with fields like 'weather' (containing nested 'city', 'temp', 'feels_like', 'humidity', 'wind_speed', 'description') or 'error', but neither the tool docstring nor parameter definitions state this structure. LLMs cannot plan downstream operations without knowing what fields to expect.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 41 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 37 | - | v1 |
Error handling returns raw error messages without guidance. If 'API key not found' or network failure occurs, the response is {'error': '...'} with no instruction for the LLM (e.g., 'Configure OPENWEATHER_API_KEY environment variable' or 'Retry in 30 seconds'). This violates the recovery-guide pattern.
No input validation or constraint documentation. The 'city' parameter accepts any string, but the code will fail on empty strings, extremely long strings, or special characters. The parameter description should specify: 'City name (1-100 characters, alphanumeric + spaces)'.
No pagination or result limiting strategy. While this single-city tool does not return lists, it does not document what happens if the API returns multiple matches or if the response is truncated. Future expansion should include guidance on handling ambiguous city names (e.g., 'Springfield' exists in many states).
The 'lang' parameter should be an enum rather than free-form string. OpenWeather API supports specific language codes (en, es, fr, de, etc.), but the tool accepts any string, inviting hallucinated invalid codes from LLMs. This violates constrained-input pattern.