高德地图
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAP_MAPS_API_KEY | Yes | Your valid Amap Maps API key obtained from the Amap Open Platform (https://lbs.amap.com/) |
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 |
|---|---|
| maps_regeocodeC | 将一个高德经纬度坐标转换为行政区划地址信息 |
| maps_geoC | 将详细的结构化地址转换为经纬度坐标。支持对地标性名胜景区、建筑物名称解析为经纬度坐标 |
| maps_ip_locationC | IP 定位根据用户输入的 IP 地址,定位 IP 的所在位置 |
| maps_weatherB | 根据城市名称或者标准adcode查询指定城市的天气 |
| maps_bicycling_by_addressA | Plans a bicycle route between two locations using addresses. Unless you have a specific reason to use coordinates, it's recommended to use this tool. |
| maps_bicycling_by_coordinatesA | Plans a bicycle route between two coordinates. |
| maps_direction_walking_by_addressA | Plans a walking route between two locations using addresses. Unless you have a specific reason to use coordinates, it's recommended to use this tool. |
| maps_direction_walking_by_coordinatesA | 步行路径规划 API 可以根据输入起点终点经纬度坐标规划100km 以内的步行通勤方案,并且返回通勤方案的数据 |
| maps_direction_driving_by_addressA | Plans a driving route between two locations using addresses. Unless you have a specific reason to use coordinates, it's recommended to use this tool. |
| maps_direction_driving_by_coordinatesA | 驾车路径规划 API 可以根据用户起终点经纬度坐标规划以小客车、轿车通勤出行的方案,并且返回通勤方案的数据 |
| maps_direction_transit_integrated_by_addressA | Plans a public transit route between two locations using addresses. Unless you have a specific reason to use coordinates, it's recommended to use this tool. |
| maps_direction_transit_integrated_by_coordinatesA | 根据用户起终点经纬度坐标规划综合各类公共(火车、公交、地铁)交通方式的通勤方案,并且返回通勤方案的数据,跨城场景下必须传起点城市与终点城市 |
| maps_distanceC | 测量两个经纬度坐标之间的距离,支持驾车、步行以及球面距离测量 |
| maps_text_searchC | 关键词搜索 API 根据用户输入的关键字进行 POI 搜索,并返回相关的信息 |
| maps_around_searchB | 周边搜,根据用户传入关键词以及坐标location,搜索出radius半径范围的POI |
| maps_search_detailB | 查询关键词搜或者周边搜获取到的POI ID的详细信息 |
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 16 tools
The tools are mostly distinct: geocoding, IP location, weather, POI search, and route planning are clearly separated. However, the route planning tools come in address/coordinate pairs for four travel modes (bicycling, walking, driving, transit), creating 8 similar tools that could be confused, though the by_address/by_coordinates suffix helps.
Most tools follow a consistent maps_<action>_by_<input> pattern (e.g., maps_direction_driving_by_address, maps_direction_driving_by_coordinates). Minor deviations exist: maps_regeocode, maps_geo, maps_ip_location, maps_weather, maps_distance, maps_text_search, maps_around_search, maps_search_detail don't follow the same verb_noun structure, but they are still readable and predictable.
16 tools is slightly above the ideal range but reasonable for a maps server covering geocoding, search, weather, and multiple route types. The 8 route-planning variants inflate the count, but each serves a distinct mode/input combination.
The server covers geocoding (forward/reverse), IP location, weather, POI search (text/around/detail), and route planning for driving, walking, bicycling, and transit. Missing features like place autocomplete or static map images are minor gaps; the core mapping workflows are well covered.