Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEATHER_API_KEY | Yes | 和风天气 API Key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherA | 获取指定城市的实时天气。 |
| get_forecastB | 获取指定城市的天气预报。 |
| get_warningsA | 获取指定城市当前生效中的天气预警。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool addresses a distinct weather information need: current conditions, forecast, and warnings. There is no functional overlap.
All tool names follow the 'get_<resource>' pattern (get_current_weather, get_forecast, get_warnings), ensuring predictability.
Three tools cover the essential weather functions (current, forecast, warnings) without being too few or excessive.
Core weather data needs are met, but optional features like historical data or air quality are absent. Minor gap, but acceptable for a focused weather server.