amap-weather-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAP_API_KEY | Yes | 高德地图开发者 API 密钥 |
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_weatherB | 获取指定城市的实时天气 Args: city: 中国城市名称，如"北京市"、"上海市"、"广州市"等 |
| get_weather_forecastA | 获取指定城市的天气预报（未来3-4天） Args: city: 中国城市名称，如"北京市"、"上海市"、"广州市"等 |
| search_cityC | 根据关键词搜索匹配的城市 Args: keyword: 城市名称关键词 |
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 serves a clearly distinct purpose: real-time current weather, multi-day forecast, and city lookup by keyword. There is no functional overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (get_current_weather, get_weather_forecast, search_city). The naming is predictable and clear.
With exactly three tools covering current weather, forecast, and city search, the server is tightly scoped for its weather information purpose. This count is minimal but sufficient and well within the 3-15 ideal range.
The server covers the core weather workflow: search for a city, get current conditions, and get a multi-day forecast. There are no obvious gaps for a general weather query service; all essential operations are present.