TravelMind MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAP_API_KEY | Yes | 高德开放平台 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeA | 将结构化地址解析为经纬度坐标,例如 '北京市朝阳区望京 SOHO' → location 'lng,lat'。 |
| regeocodeA | 将经纬度坐标转换为行政区划地址(街道级精度)。例如 '116.481,39.990' → '北京市朝阳区望京街道...' |
| text_searchA | 在指定城市内按关键词搜 POI(酒店/餐厅/景点/地标)。返回前 10 条。 |
| around_searchB | 在坐标 + radius 范围内搜周边 POI,例如酒店附近 1km 内的餐厅。 |
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 4 tools
All four tools have clearly distinct purposes: geocode converts address to coordinates, regeocode does the reverse, text_search searches POIs by keyword in a city, and around_search finds POIs near a coordinate. No overlap or ambiguity.
All tool names follow a consistent snake_case pattern with descriptive verbs (geocode, regeocode, text_search, around_search). The use of 'regeocode' as a prefix variant is coherent within the domain.
The server has 4 tools, which is perfectly scoped for a geocoding and POI search service. Each tool covers a fundamental operation without being excessive or insufficient.
The tool set covers forward and reverse geocoding as well as two common POI search modes (keyword and proximity). A minor gap is the lack of a tool to retrieve details for a specific POI, but the existing tools still provide useful results.