Skip to main content
Glama
Weather MCP Server

Weather MCP Server

by WYHEF

get_current_weather

Retrieve current weather conditions for a specified city, supporting Chinese and English city names, to answer real-time weather queries.

Instructions

Get current weather information for a city

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_current_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesThe city name to get weather for (e.g., "Beijing", "New York")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing beyond the basic action. It does not mention units (Celsius/Fahrenheit), data source or freshness, how unknown or ambiguous city names are handled, or what the response contains — all relevant for a live-data lookup.

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?

One short sentence, front-loaded with the verb and resource, with no redundant or filler wording. Nothing could be trimmed without losing information.

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?

For a one-parameter lookup with no output schema and no annotations, the description covers the action but leaves open return format, units, and failure behavior. It is minimally sufficient to call the tool correctly but not sufficient to interpret results confidently.

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 'city' parameter is documented with example values in the schema itself. The description adds no meaning beyond that, which is the baseline expectation when the schema already does the work.

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 pairs a specific verb ('Get') with a specific resource ('current weather information') and scope ('for a city'), so an agent immediately knows what it retrieves. There are no sibling tools to distinguish from, which is the only thing keeping it from 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 Guidelines3/5

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

Usage is implied by the word 'current' — an agent can infer this is for present conditions rather than forecasts or historical data — but the description never states when to use it, when not to, or names any alternative. Adequate only because the tool's intent is largely self-evident.

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