A demonstration MCP server providing weather tools via SSE transport
Two tools with basic verb-noun naming (get_alerts, get_forecast) and minimal descriptions. Both have input schemas with type definitions and parameter descriptions, meeting baseline requirements. No output schemas documented. Tool implementations are stubs returning hardcoded strings, indicating incomplete development. No error handling, no pagination support, no composition guidance.
Get weather alerts for a US state.
Get weather forecast for a location.
Tool descriptions critically short (10-11 chars). Both tools fail to explain WHEN to use them, WHAT they return, or dependencies. LLMs cannot reliably select between tools with such minimal context.
No output schemas documented. LLMs cannot plan downstream calls or extract structured data. Both tools return bare strings ('state', 'latitude') instead of weather data objects.
Tool implementations are stubs. get_alerts returns the input state string; get_forecast returns the literal string 'latitude'. No actual API calls to NWS_API_BASE. Tools are non-functional.
No error handling or recovery guidance. If NWS API fails or input is invalid, LLM receives no actionable error message. No retry logic, no fallback suggestions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
get_alerts accepts only 'state' (string) with no enum constraint. LLM can pass invalid state codes (e.g., 'XX', 'California'). No validation or constraint documentation.