Weather MCP Server that provides weather alerts and forecasts using the National Weather Service API
Two tools with clear verb-noun naming (get_alerts, get_forecast) and basic input schemas using Zod. Descriptions are present but minimal (18-24 chars, below the 50-200 char LLM-optimized baseline). Parameter descriptions exist but lack detail on constraints, formats, and error recovery. No output schema documentation. Error handling returns text responses but lacks actionable guidance for LLM recovery. Schemas are properly typed with constraints (latitude/longitude bounds, state length), but descriptions do not explain these constraints in natural language.
Get weather alerts for a state
Get weather forecast for a location
Tool descriptions are too brief (18-24 chars). LLM-optimized descriptions should be 50-200 chars and explain WHAT the tool does, WHEN to use it, and any prerequisites. Current descriptions lack context for tool selection.
Parameter descriptions lack constraint details. 'Two-letter state code (e.g. CA, NY)' is good, but latitude/longitude descriptions do not mention the -90/90 and -180/180 bounds in natural language. LLMs cannot read JSON Schema constraints, they rely on description text.
No output schema documentation. Callers cannot predict the structure of returned forecast periods, alert fields, or error responses. LLMs need documented return types to plan downstream tool calls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Error responses lack actionable recovery guidance. When NWS API fails or coordinates are unsupported, responses return plain text but do not suggest next steps (e.g., 'Try a different location' or 'Check that coordinates are within the US'). Errors should guide LLM recovery.
No tool annotations (readOnlyHint, idempotentHint). Both tools are read-only and idempotent, but this is not declared in the schema. Tool annotations help clients optimize caching and retry logic.