Weather MCP Server that provides real-time weather alerts and forecast data from the National Weather Service (NWS) API
The weather server defines two tools with explicit schemas and descriptions. Both tools have valid Zod-based input schemas with proper type constraints (min/max for coordinates, length for state code). Descriptions are present but minimal (11-12 words each). Parameter descriptions are adequate but lack detail about use cases, error conditions, or expected behavior. Output is unstructured text rather than typed JSON objects, requiring LLMs to parse plain text. Error handling returns text responses without actionable recovery guidance. The server lacks pagination, result limits, and field naming consistency across related tools. Schema constraints are present in code but descriptions could better reflect them.
Get weather alerts for a state
Get weather forecast for a location
Output is unstructured plain text, not typed JSON. Descriptions like 'Active alerts for CA:\n\nEvent: Severe Thunderstorm...' require LLM parsing. No documented output schema showing alert fields, forecast structure, or field types.
Tool descriptions lack context for tool selection. 'Get weather alerts for a state' and 'Get weather forecast for a location' do not explain WHEN to use each tool, what distinguishes them, or what the output represents. Descriptions should be 50-200 chars with actionable intent.
No result limiting or pagination. If get-alerts returns 100+ active alerts, the entire result is stringified and sent to the LLM. No documented limit, offset, or next_cursor. Large results exhaust context and invite hallucination.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 56 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 40 | - | v1 |
Error responses are bare text strings with no recovery guidance. Example: 'Failed to retrieve grid point data for coordinates: 35.6762, 139.6503. This location may not be supported by the NWS API (only US locations are supported).' Does not tell the LLM whether to retry, ask the user, or try alternative coordinates.
Parameter descriptions are minimal. 'Latitude of the location' and 'Longitude of the location' do not explain coordinate systems, precision expectations, or what 'location' means in context. State code description 'Two-letter state code (e.g. CA, NY)' uses example values instead of listing valid values or linking to a reference.
No error classification. LLMs cannot determine if HTTP 404 (points not found) is retryable, user-fixable (bad coordinates), or fatal. Should return structured error with type field: {type: 'invalid_coordinates', retryable: false, userFixable: true}.