OpenWeather MCP Server - provides weather and air quality data tools via MCP protocol using Spring Boot and Spring AI
Single tool with basic definition but significant gaps in production readiness. The getCurrentWeather tool has a verb-noun name (good) and input schema with typed parameters (good), but lacks a complete, LLM-optimized description. Parameter descriptions are minimal (1-3 words each), and there is no documented output schema. No error handling guidance, no parameter constraints (latitude/longitude ranges), and no information about what the tool returns or when to call it. The tool definition is visible in source code and properly registered via Spring AI's MethodToolCallbackProvider, but falls short of production quality for agent use.
Get current weather data for a location
Tool description is too short and lacks LLM-critical context. 'Get current weather data for a location' (52 chars) is minimal; should explain WHEN to call this tool, WHAT it returns, and any prerequisites. LLMs cannot distinguish this from alternative weather tools or plan multi-step queries without richer context.
No documented output schema. The tool returns weather data (visible in model classes: Main, AqiMain), but the MCP tool definition does not declare what fields the caller should expect. LLMs cannot extract temperature, humidity, or pressure fields if they are not documented in the output schema.
Parameter descriptions are placeholder-quality. 'Latitude of the location' and 'Longitude of the location' lack constraints (valid range: -90 to 90, -180 to 180 respectively). LLMs may pass out-of-range values; no validation guidance is provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 45 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
No error handling guidance. If a coordinate is invalid or the weather service is unavailable, the tool returns an error with no recovery hint. LLMs need actionable next steps: 'Check latitude is between -90 and 90' or 'Retry in 30 seconds' or 'Use a different location'.
Input schema is incomplete. While 'latitude' and 'longitude' are typed as number, there are no bounds (minimum, maximum, or exclusiveMinimum/exclusiveMaximum). JSON Schema allows numeric constraints; they should be present.