MCP server providing weather alerts and forecasts using the National Weather Service API
This server defines 2 weather tools with basic but incomplete definitions. Tool names follow verb_noun conventions (get_alerts, get_forecast) which is good. However, descriptions are minimal (27-35 characters), falling well below the rubric baseline of 194 chars average. Critical gaps: no output schemas documented, no pagination support, no error handling guidance, and parameters lack depth (e.g., state parameter has no enum constraint for valid US state codes). The tools are read-only and stateless, which is appropriate, but the LLM-facing definitions need substantial improvement for production use.
Get weather alerts for a US state
Get weather forecast for a location
Tool descriptions are extremely brief (27-35 chars vs rubric baseline 194 chars). No guidance on when to use each tool, what it returns, or dependencies.
No output schema documented for either tool. Both return plain strings, but LLMs need to know the expected structure, format, and what fields to extract for downstream operations.
'state' parameter in get_alerts lacks enum constraint. Should declare valid values (AL, AK, AZ, ... WY) so LLMs pick from canonical set rather than hallucinating invalid codes.
No error handling or recovery guidance. Code catches exceptions silently (return None) and tools return plain strings like 'Unable to fetch alerts'. LLMs cannot determine if error is retryable, what to do next, or whether to try an alternative tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 39 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | - | v1 |
get_forecast hardcodes limit to 5 periods (periods[:5]) with no way for LLM to control results. No pagination or limit parameter. If user asks for 10-day forecast, tool silently truncates.
Latitude/longitude parameters lack range constraints. Descriptions should specify valid ranges (lat: -90 to 90, lon: -180 to 180) to prevent LLMs from passing invalid coordinates.