Skip to main content
Glama
Sign In
mcp-map-server

mcp-map-server

by ganyu123456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

map_reverse_geocode

Reverse geocode latitude and longitude coordinates into readable addresses. Supports AMap and Baidu platforms with appropriate coordinate systems.

Instructions

逆地理编码：将经纬度坐标转换为可读地址。坐标格式为'经度,纬度'（如'116.481,39.990'）。注意坐标与平台绑定：高德为 GCJ-02，百度为 BD-09，不可跨平台混用。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "map_reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes坐标，格式'经度,纬度'，如'116.481,39.990'
platformNoMap platform to use. Defaults to 'amap'.amap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the coordinate format and the critical platform-specific coordinate system constraint (GCJ-02 for Amap, BD-09 for Baidu) and warns against cross-platform mixing. However, it does not mention return format or other behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the purpose and then providing key usage constraints. Every sentence is necessary and succinct, with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, and the description does not explain what the tool returns (e.g., address structure). Given the complexity (different coordinate systems), the description is informative but incomplete regarding the output, which an agent needs to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline descriptions for both parameters. The description adds value by explaining the coordinate format and platform-specific coordinate bindings beyond the schema, which is helpful for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: reverse geocoding (converting coordinates to readable address). It specifies the coordinate format and warns about platform coordinate system differences, making the purpose unambiguous and distinct from siblings like map_geocode (forward geocoding).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (convert coordinates to address) but does not explicitly state when not to use or provide comparisons to sibling tools. It includes a platform binding caution but lacks explicit usage context or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools