Weather forecast MCP server using the YR weather API
The YR server defines 2 weather tools with explicit schemas and descriptions. However, multiple critical issues prevent a higher score: (1) descriptions are brief but adequate (50-60 chars each), meeting minimum thresholds; (2) parameter descriptions exist but lack critical constraint details like valid range, format, or behavior; (3) the 'altitude' parameter is marked optional in both tools but the implementations don't actually use it when passed (see line 'make_weather_forecast_request' calls omit altitude), creating a silent contract violation; (4) output schema is completely undocumented, neither tool declares what fields the JSON response contains, forcing LLMs to guess; (5) error handling is generic ('Unable to fetch weather forecast') with no recovery guidance; (6) the tools are minimal duplicates that differ only in the 'type' parameter, suggesting the interface could be unified into a single parameterized tool. The naming (get_weather_forecast_compact vs get_weather_forecast_complete) is clear and verb-prefixed, which is a strength. Overall, this is a functional but under-engineered implementation suitable for personal use, not production agents.
Get a compact weather forecast for a specified location
Get a complete weather forecast for a specified location
Altitude parameter accepted but silently ignored in implementation
Output schema completely undocumented
Generic error message with no recovery guidance
Parameter descriptions lack constraint details
Two nearly identical tools suggest design could be unified
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 43 | - | v1 |