MCP server exposing Prague's Golemio API for AI assistants
Five tools with consistent naming (verb_noun pattern: get_*) and basic descriptions. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are generic (avg ~60 chars, well below the 194-char baseline for A+ tools) and lack actionable context. No output schemas documented. Error handling returns raw API status codes or generic messages without recovery guidance. No parameter constraints (enums, ranges, patterns) despite accepting free-form strings like 'latlng' and 'districts'. Missing idempotency hints, prerequisites, and dependency documentation. Tools accept coordinates as unvalidated strings, inviting malformed input.
Get air quality monitoring stations in Prague.
Get bicycle counting stations in Prague.
Get bicycle traffic detection data from counting stations.
Get parking lot information and availability in Prague.
Get sorted waste collection stations in Prague.
Output schemas not documented. Tools return formatted strings (e.g., 'Name: X\nID: Y') instead of structured JSON. LLMs cannot parse or chain results reliably.
Descriptions are generic and lack actionable context. E.g., 'Get bicycle counting stations in Prague' does not explain when to use this vs other tools, what the response contains, or prerequisites. Avg 45 chars vs 194-char baseline.
No parameter constraints. 'latlng' accepts any string; 'districts' accepts any comma-separated value; 'range' and 'limit' have no min/max bounds. LLMs can pass invalid values (negative ranges, absurd limits) without validation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Error handling returns raw HTTP status codes ('API error: 404') or generic messages ('Error: GOLEMIO_API_KEY not set') without recovery guidance. LLM cannot determine if error is retryable or what to do next.
API key exposed via environment variable without server-side injection pattern. If agent logs or traces tool calls, GOLEMIO_API_KEY could leak. No scope declarations or permission gates.