A Spring Boot-based MCP server providing weather and air quality tools via OpenMeteo API
Two tools with basic verb-noun naming (getWeatherForecastByLocation, getAirQuality) but descriptions are in Chinese and extremely brief (10-15 chars in English equivalent). Input schemas present with latitude/longitude parameters typed as double with minimal descriptions. No output schemas documented. No error handling guidance. No parameter constraints (e.g., valid lat/lon ranges). Tool composition is reasonable (two separate read-only operations), but descriptions fail to meet the 10-1024 character guideline and lack actionable context for LLM selection.
获取指定位置的空气质量信息(模拟数据)
获取指定经纬度的天气预报
Descriptions are non-English and critically brief (10-15 chars). Fail minimum 10-1024 char guideline and provide no context for LLM tool selection.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields from responses.
Parameter descriptions lack constraints. latitude/longitude have no range validation (valid: -90 to 90, -180 to 180), format hints, or examples.
No error handling guidance. If API call fails or coordinates are invalid, LLM receives no recovery path.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
Tool names use camelCase (getWeatherForecastByLocation) instead of snake_case (get_weather_forecast_by_location). Inconsistent with LLM conventions.