MCP Weather Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_weatherA | 获取指定城市的当前天气信息。 |
| get_forecastB | 获取指定城市未来几天的天气预报。 |
| temperature_convertA | 摄氏度与华氏度互相转换。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| travel_advisor | 生成旅行天气咨询的提示词 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_cities | 返回支持查询天气的热门城市列表 |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_forecast for future days, get_weather for current conditions, and temperature_convert for unit conversion. No overlap exists.
All tools use snake_case, but two follow verb_noun pattern (get_forecast, get_weather) while one uses noun_verb (temperature_convert), a minor inconsistency.
3 tools is slightly below average for a weather server, but still reasonable for core functionality (current, forecast, conversion). The count feels lean but not insufficient.
Covers basic current weather and forecast, plus a unit converter. Missing features like alerts or historical data, but the essential weather information needs are met.