MCP server for querying weather data from QWeather API
Two tools with minimal descriptions (both under 100 chars) and incomplete parameter documentation. Input schemas present but lack detail. No output schema documentation. Error handling returns raw strings without guidance. No parameter constraints (e.g., day enum). Tool descriptions do not explain WHEN to use each tool or what distinguishes them. Parameter 'location' lacks format guidance (Chinese city names only?). No mention of API dependencies or prerequisites.
Get the weather of a place for the following consecutive days.
Get the weather of a place for the moment
Parameter 'day' in get_weather_day lacks enum constraint. Description says 'supported: 3/7/10/15/30 days' but no formal enum in schema. LLMs will pass invalid values (e.g., 5, 14) causing API errors.
No output schema documented. Tools return unstructured strings (e.g., 'Unable to fetch weather', raw JSON from API). LLMs cannot parse results reliably or chain to downstream tools.
Parameter 'location' description is vague ('the name of province, city or district'). No guidance on format, language (Chinese only?), or examples. LLMs may pass English city names causing lookup failures.
Error handling returns raw exception strings ('Location not found: {name}', 'Unable to fetch weather'). No recovery guidance. LLMs cannot determine if error is retryable or user-fixable.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Tool descriptions do not distinguish use cases. Both tools fetch weather; description should explain when to call get_weather_now vs get_weather_day (e.g., 'for current conditions' vs 'for forecast').