Get a multi-day weather forecast for any Chinese city by name or adcode, providing upcoming weather conditions to support trip planning and daily decisions.
查询指定城市未来几天的天气预报。
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | 城市名称或 adcode（行政区划代码） |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. '查询' implies a read-only operation and the forecast scope is stated, but the description does not mention response format, units, or how city name versus adcode is handled. Adequate for a simple query tool but not richly transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It efficiently conveys the operation, resource, and temporal scope without unnecessary details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description plus input schema are sufficient to make a correct first call. Minor gaps like units or forecast length are not critical given the tool's low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single parameter is already documented by the schema. The description adds the 'next few days' time scope but provides no additional semantics about the city parameter beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: '查询' (query) the weather forecast for a specified city over the next few days. It is clearly distinct from the sibling geocoding, search, and direction tools, so an agent can immediately identify what this tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended usage is clear: use this tool when a weather forecast for a city is needed. No explicit when-not or alternative conditions are stated, but no sibling tool offers weather functionality, so routing is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.