A Spring Boot-based MCP server and client implementation using Spring AI framework with weather tools
Single tool (getCurrentWeather) with minimal definition quality. Tool has a basic description (18 chars, below 20-char threshold) and a single parameter with type but no description. No output schema documented. No error handling guidance. Tool definition appears to be inferred from Spring AI annotations rather than explicitly registered with full MCP schema. This server does not meet production baseline standards.
Get the current weather information by city name.
Tool description is 18 characters ('Get the current weather information by city name.'), below 20-char minimum. Descriptions under 20 chars cannot adequately guide LLM tool selection.
Parameter 'city' has type (string) but NO description. LLMs cannot infer whether 'city' means city name, city code, or city ID.
No output schema documented. LLMs cannot plan downstream calls or extract expected fields (temperature, humidity, conditions, etc.).
No error handling guidance. If city is not found or API fails, LLM receives no recovery hint.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | 2026-07-28+ | v2 |
Tool definition inferred from Spring AI MethodToolCallbackProvider annotations, not explicitly visible in MCP schema registration.