Real-time weather query MCP server based on HelloAgents framework
This server has critical gaps in definition quality. While three tools are present and registered, they suffer from incomplete schemas, minimal descriptions, and lack of proper error handling guidance. The tool descriptions are in Chinese and very short (10-30 chars), well below the 50-200 char LLM-optimized baseline. Only one tool (get_weather) has any input schema visible, and even that schema is minimal. No parameter descriptions are provided. No output schemas are documented. The server appears to be a basic wrapper around a weather API with minimal production-grade tool design patterns applied.
获取服务器信息
获取指定城市的当前天气
列出所有支持的中文城市
Tool descriptions are extremely minimal (10-30 characters) and lack actionable context for LLM selection. Descriptions must be 50-200 chars and explain WHAT the tool does, WHEN to use it, and any prerequisites.
Only get_weather has an input schema visible; list_supported_cities and get_server_info have no documented input schemas. Missing schemas prevent LLMs from understanding what parameters are required or optional.
No parameter descriptions are provided. The 'city' parameter in get_weather lacks explanation of format, valid values, or error cases. LLMs cannot reliably infer that both Chinese and English city names are accepted without explicit guidance.
No output schemas are documented for any tool. LLMs cannot plan downstream calls or extract structured data without knowing what fields to expect from responses.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 32 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 31 | - | v1 |
Descriptions are in Chinese ('获取指定城市的当前天气', '列出所有支持的中文城市', '获取服务器信息'). English descriptions are necessary for LLM models which predominantly operate in English and for tool discoverability.
No error handling guidance is documented. If an invalid city name is provided or the weather API is unavailable, there is no recovery path or explanation for what the LLM should do next.