Skip to main content
Glama

Weather Forecast MCP

Query Weather

query_weather

查询全球城市的实时天气和未来几天预报。city城市名中英文均可,days预报天数1~7默认3天。主源Open-Meteo,备源wttr.in。

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": "<city>"
    },
    "name": "query_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes城市名,中文英文均可,如 "青岛"、"北京"、"Tokyo"
daysNo预报天数,1 到 7,默认 3 天

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / city / description
      Added value: +"城市名,中文英文均可,如 \"青岛\"、\"北京\"、\"Tokyo\""
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • addedInput schema / properties / days / description
      Added value: +"预报天数,1 到 7,默认 3 天"
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / title
      Removed value: -"query_weatherArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It helpfully discloses data sourcing with a primary/backup arrangement ('主源Open-Meteo,备源wttr.in'), which hints at fallback behavior, but says nothing about rate limits, caching, failure handling, or freshness guarantees.

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?

Three short sentences, front-loaded with purpose before parameter notes and sourcing. Tight overall, with only mild repetition of what the schema already states.

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

Completeness4/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, and parameters are fully covered. Purpose, scope, and source fallback are all present; only operational details like rate limits or error behavior are absent.

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 100%, so both parameters are already fully documented in the schema. The description restates the same facts (bilingual city names, days 1–7 defaulting to 3) rather than adding new meaning, which is the baseline case.

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?

The description names a specific verb and resource ('查询全球城市的实时天气和未来几天预报') and scopes it to global cities, covering both current conditions and multi-day forecast. It is unambiguous, though it does not differentiate from any sibling (none exist).

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

Usage Guidelines3/5

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

Usage is only implied by the tool's single obvious purpose; there are no explicit when-to-use/when-not-to-use statements, no prerequisites, and no alternatives named. Adequate for a simple lookup tool but nothing more.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.