Skip to main content
Glama
DongDong1997

Weather MCP Server

by DongDong1997

get_current_weather

Retrieves real-time weather data for any city using name, coordinates, or location ID. Supports multiple languages and unit systems.

Instructions

获取指定城市的实时天气。

Args:
    location: 城市名称(如"北京")、经纬度(格式"lng,lat"如"116.41,39.92")或 Location ID。
    lang: 可选,多语言设置(如 "zh"、"en"),不传则用服务端默认。
    unit: 可选,数据单位,"m" 公制(默认)/"i" 英制。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
unitNo
locationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as data freshness, accuracy, rate limits, or side effects. It only covers parameter formats.

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?

The description is concise and front-loaded with the main purpose. The parameter documentation is structured clearly, though it follows a standard docstring format.

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?

The tool has an output schema but the description does not explain return values or behavior. Given the complexity and lack of annotations, more context on behavior would improve completeness.

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

Parameters4/5

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

With 0% schema description coverage, the description adds significant value by detailing the three formats for location, multi-language options for lang, and metric/imperial units for unit, beyond the basic type definitions.

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

Purpose5/5

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

The description clearly states it gets real-time weather for a specified city, using a specific verb and resource. It distinguishes from siblings like get_forecast and get_warnings.

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?

The description implies usage for current weather but does not explicitly state when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DongDong1997/weather'

If you have feedback or need assistance with the MCP directory API, please join our Discord server