A Model Context Protocol (MCP) server for weather information using the Weatherstack API
Single tool 'currentWeather' has a basic description but lacks critical schema documentation. Input schema visible in code shows only 'city' parameter with minimal type info. No output schema documented. Parameter description is generic (10 chars baseline violated). No error handling guidance for LLM recovery. Tool naming is acceptable (verb_noun pattern) but descriptions fall short of production baseline (194 chars avg; this is ~50 chars). No pagination, no structured output guidance, no idempotency markers.
Get current weather for a city or location
No output schema documented. LLM cannot plan downstream operations or extract structured data from weather response.
Tool description is 50 chars; baseline is 194 chars. Lacks WHEN to use, WHAT it returns, and prerequisites (API key requirement).
Parameter 'city' description is 10 chars ('City name (e.g., "New York")' is ~30 chars but lacks format constraints, min/max length, or handling of multi-word cities).
No error handling guidance. Errors like 'API key error' or 'City not found' are returned as raw messages without recovery hints (e.g., 'Try a different city name' or 'Check WEATHERSTACK_API_KEY').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
Hardcoded default API key in source (a07119cef2e19d493340c892615a1397) is a security anti-pattern. Credentials must never be in code; use environment-only injection.