An MCP server that provides weather data tools using the OpenWeatherMap API, designed to work with an LLM agent via FastAPI and SSE transport
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (get_current_weather, get_forecast), which is good. However, parameter descriptions are minimal (e.g., 'The name of the city' lacks context about format, length, or valid values). No output schemas documented. No error handling guidance. No tool annotations. Descriptions are adequate length (50-60 chars) but lack actionable detail about when to use each tool vs. the other.
Get the current weather for a specific city.
Get the weather forecast for a specific city.
No output schemas documented. LLMs cannot plan downstream operations or extract specific fields without knowing what get_current_weather and get_forecast return.
Parameter descriptions lack actionable constraints. 'The name of the city' does not specify format (e.g., 'English name only'), length limits, or handling of multi-word cities (e.g., 'New York' vs 'new york'). LLMs will guess.
No distinction between tools. Both get_current_weather and get_forecast accept 'city' and return weather data. The description does not explain when to use get_forecast over get_current_weather (e.g., 'Use for multi-day outlook' vs 'Use for today only').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
No error handling guidance. If a city is not found or the API fails, the LLM has no recovery path. Descriptions should hint at fallback strategies (e.g., 'If city not found, try a larger region or country name').
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Both tools are read-only and idempotent, but this is not declared in the schema. Modern MCP clients use these hints for safety and optimization.