AMap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAP_KEY | Yes | Your API key from AMAP open platform |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_weatherB | The weather service of Amap. Query the weather of a given city. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on weather queries.
The single tool name follows a clear verb_noun pattern (query_weather), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and descriptive.
One tool is too few for a server named 'AMap MCP Server', which suggests a broader mapping or location service domain. A single weather query tool feels thin and incomplete for this apparent scope.
The server is severely incomplete for a mapping service domain. There are obvious gaps such as geocoding, routing, place search, or map display tools. The single weather tool does not provide meaningful coverage of the expected functionality.