Convert GCJ-02 coordinates into detailed structured addresses and administrative area information, enabling location-based applications to resolve geographic coordinates into readable location data.
逆地理编码：将高德经纬度坐标（GCJ-02）转换为详细结构化地址和行政区划信息。
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes | 经纬度坐标，格式"经度,纬度"，如"116.480881,39.989410" |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It adds useful behavioral context by specifying the GCJ-02 coordinate system and the output type, but it does not disclose potential failure modes, coordinate validation rules, authentication needs, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It communicates the operation, input, and output efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, low-complexity tool, the description provides the essential context: input coordinate system, conversion direction, and output content. The schema fully documents the parameter, though a small amount of sibling routing or return-format detail could make it more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single parameter location already includes a clear format and example. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific operation and resource: reverse geocoding converts GCJ-02 coordinates into structured address and administrative-division information. This clearly distinguishes it from forward geocoding siblings like maps_geo.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies the use case: use it when you have Gaode coordinates and need a structured address. However, it does not explicitly mention when not to use it or name alternatives such as maps_geo, maps_around_search, or maps_ip_location.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.