Weather MCP Server

get_weather

Fetch current weather for a specified city using English or Chinese names; Chinese city names are translated to English automatically.

Instructions

Get current weather for a city. Chinese city names are automatically translated to English.

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": "get_weather"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	City name in English or Chinese

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the non-obvious Chinese-to-English auto-translation behavior, which an agent could not infer from the schema, but it says nothing about units, error handling, or what happens with unrecognized cities.

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

Conciseness5/5

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

Two short sentences, zero waste, with the core purpose front-loaded and the translation caveat second. Every sentence earns its place.

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?

For a one-parameter, annotation-free tool with no output schema, the description covers purpose and the notable input-handling behavior. Return format need not be explained since no output schema exists, though units and error behavior remain unstated.

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% and the single parameter is already documented as 'City name in English or Chinese'. The description adds only the auto-translation detail, so baseline 3 applies — the schema does the heavy lifting.

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 (Get) and resource (current weather) plus its scope (for a city). There are no sibling tools to distinguish from, so the lack of differentiation is not a fault, but it also doesn't need to do more than it does.

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 implied by 'Get current weather for a city' — the agent can infer it invokes this for any city weather lookup. There are no alternatives or exclusions to state, so no when-not guidance is possible, but nothing confirms scope limits either (e.g., current only vs forecast).

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

get_weatherA