Skip to main content
Glama
Sign In
Agent中国通

Agent中国通

by FRANhss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

高德坐标转地址

cn_amap_regeocode
Read-onlyIdempotent

Convert GPS coordinates to Chinese addresses and administrative divisions. Supports base or detailed output with surrounding information.

Instructions

把经纬度反查为中文地址和行政区划。需要 AMAP_API_KEY。

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": {
      "longitude": "<longitude>",
      "latitude": "<latitude>"
    },
    "name": "cn_amap_regeocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
longitudeYes经度，例如 116.397428
latitudeYes纬度，例如 39.90923
extensionsNo返回信息范围，默认 base；all 会包含更详细周边信息。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate readOnly, non-destructive, idempotent, and open world behavior. The description adds the critical requirement of an AMAP_API_KEY, which is not in annotations. This provides additional behavioral constraint beyond what annotations offer. No contradictions.

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?

Two short, front-loaded sentences: first states purpose, second states prerequisite. No wasted words.

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

Completeness2/5

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

Despite clear purpose and good schema, the description lacks any indication of the output format or structure. With no output schema present, the description should at least mention what kind of data is returned (e.g., province, city, district). This gap reduces completeness for an AI agent.

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

Parameters3/5

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

Schema coverage is 100% (all 3 parameters have descriptions). The description does not add any parameter-specific information beyond what the schema already provides, so baseline 3 is appropriate.

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 converts coordinates to Chinese address and administrative division, using a specific verb '反查'. It distinguishes from sibling tool cn_amap_geocode (which does the reverse) by mentioning '反查', implying the opposite direction.

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 usage for geocoding coordinates to Chinese addresses and mentions a prerequisite (AMAP_API_KEY), but does not provide explicit when-to-use or when-not-to-use guidance versus alternatives. The usage is clear from context but not elaborated.

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