MCP server for querying weather data via OpenWeatherMap API
This server has critical gaps in definition quality. All three tools lack parameter descriptions (position, weather, forecast), which is a hard failure per the rubric. Tool descriptions themselves are missing entirely. Schemas are present (Zod-based) but lack human-readable documentation. The server provides no guidance on when to use each tool, what they return, or how they relate to each other. No error handling, no output schema documentation, and no security considerations. Parameter descriptions in the Zod schemas are null (literal nulls in the tool definitions), so LLMs receive no context on what 'query', 'lat', or 'lon' actually mean beyond their types.
All three tools lack non-empty descriptions. HARD FAILURE per pattern:tool-description. Without descriptions, LLMs cannot determine when or why to select each tool.
All parameter descriptions are null. The Zod schemas define query, lat, and lon but provide zero documentation on what they mean, their valid ranges, units, or constraints. Per pattern:tool-description, every parameter must have a non-empty description.
No output schema documentation. Tools return JSON.stringify results as plain text, but LLMs have no documentation on what fields to expect (e.g., from 'position', does the response include both city and coordinates? from 'weather', what weather fields are returned?). Per pattern:tool, output schemas must be documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 30 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 33 | - | v1 |
No error handling or recovery guidance. If OpenWeather API fails (invalid API key, rate limit, network error), the agent receives a raw Error object. Per pattern:recovery-guide, errors must tell the LLM what to do next.
API key injection via environment variable lacks documentation. Users installing this server need to know OPENWEATHER_API_KEY is required, but this is not stated in any tool description or server documentation.
Parameter constraints missing. 'lat' and 'lon' should be documented as numbers in range [-90, 90] and [-180, 180] respectively. 'query' in position() could accept various formats (city name, 'city, country'). No guidance provided.
No tool composition guidance. The 'position' tool is obviously a prerequisite for 'weather' and 'forecast', but this dependency is never documented. Agents cannot infer the workflow without hints in descriptions.