Skip to main content
Glama

get_city_weather

Retrieves current weather and multi-day forecasts for Chinese cities, including Beijing, Shanghai, Guangzhou, Shenzhen, and Chengdu, by city name.

Instructions

查询城市天气,支持中文城市:北京/上海/广州/深圳/成都等

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city_name": "<city_name>"
    },
    "name": "get_city_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
city_nameYes
forecast_daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and discloses almost nothing: no units (Celsius/Fahrenheit), no data source or freshness, and no behavior when the city is unsupported or misspelled. Only the accepted input locale is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that front-loads the verb and resource with no filler. The trailing "等" (etc.) leaves the supported-city list open-ended, but the sentence is otherwise efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. However, for a weather tool with zero annotation coverage, the omission of units, the meaning of forecast_days, and failure behavior leaves genuine gaps an agent would need filled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds real meaning for city_name by showing that Chinese city names are accepted and giving examples, but forecast_days is never mentioned, leaving half the parameters documented only by a bare title and a default of 1.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"查询城市天气" states a specific verb and resource, and the city examples make the scope of the tool concrete. It does not explicitly distinguish itself from the web_search sibling, which could plausibly also answer weather questions, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not guidance and never mentions the alternatives (calculator, web_search). The Chinese-city examples imply a usage context but do not tell an agent when this tool is the right choice over a general search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools