Weather MCP Server providing access to US National Weather Service data
Two tools with clear verb-noun naming (get-alerts, get-forecast) and basic descriptions. Both have input schemas with type constraints (Zod validation visible). However, descriptions are minimal (under 100 chars), parameter descriptions lack context about expected formats and use cases, and output schemas are not documented. Error handling returns text responses but lacks actionable recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.
Get weather alerts for a state
Get weather forecast for a location
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting). Clients must infer from examples or trial-and-error.
Tool descriptions are under 100 characters and lack context. 'Get weather alerts for a state' does not explain when to use this vs other tools, what format the state param expects, or what the response contains.
Parameter descriptions are minimal. 'Two-letter state code (e.g. CA, NY)' includes an example value that LLMs may reuse literally. Should use enum constraint instead. Latitude/longitude descriptions lack context about coordinate system or supported regions.
Error responses are generic text ('Failed to retrieve alerts data', 'This location may not be supported by the NWS API'). No recovery guidance or error classification. LLM cannot determine if error is retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
No tool annotations despite both tools being read-only. Missing readOnlyHint and idempotentHint annotations prevent agents from optimizing caching and retry strategies.