Amap (Gaode Maps) MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Amap (高德) 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| locate_ipC | 获取用户的 IP 地址定位信息，返回省市区经纬度等信息。 |
| search_nearbyB | 根据经纬度和关键词进行周边搜索，返回指定半径内的 POI 列表。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| assistant | 高德地图智能导航助手，支持IP定位、周边POI查询等 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one retrieves location data from an IP address, while the other searches for points of interest near given coordinates. There is no overlap in functionality or ambiguity in their intended use.
Both tools follow a consistent verb_noun naming pattern (locate_ip and search_nearby), using clear, descriptive verbs that align with their actions. The naming style is uniform and predictable across the set.
With only two tools, the server feels under-scoped for a mapping service like Amap, which typically involves broader functionality such as routing, geocoding, or traffic data. This limited set may hinder agents from performing comprehensive mapping-related tasks.
The toolset is severely incomplete for a maps domain, lacking essential operations like geocoding addresses, calculating routes, or retrieving traffic information. Agents will face significant gaps when trying to handle common mapping workflows.