An MCP server that provides weather forecasts and geocoding for Japanese locations using Open-Meteo APIs
Two tools with basic verb-noun naming (get_coordinates, get_forecast) and present descriptions. However, input schemas lack parameter descriptions entirely, the JSON Schema shows only type and description at tool level, not per-parameter. Output schemas are undocumented. Error handling returns generic text ('Unable to resolve coordinates') without recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Descriptions are adequate (60 - 80 chars) but lack WHEN/WHY context. Per-parameter descriptions are completely absent, violating pattern:tool-description. This is a D-grade server with incomplete schema documentation.
Resolve Japanese location names into latitude and longitude using Open-Meteo geocoding
Get weather forecast for a location
Input parameters lack descriptions. 'query' and 'latitude'/'longitude' have no per-parameter descriptions explaining what values are valid, expected format, or constraints.
Output schemas are completely undocumented. Callers cannot see what fields get_coordinates or get_forecast return, forcing LLMs to guess structure and plan downstream calls blindly.
Error messages are generic and non-actionable. 'Unable to resolve coordinates for this location' does not guide the LLM on what to try next (e.g., try a different location name, check spelling, or use a broader search).
No tool annotations. Tools lack readOnlyHint, idempotentHint, or destructiveHint, preventing agents from reasoning about safety and retry behavior.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Tool descriptions lack WHEN/WHY context. 'Resolve Japanese location names into latitude and longitude' states WHAT but not WHEN to call it vs. alternatives or what prerequisites exist.