Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_geo_cn_city

Look up Chinese city details including province, tier, coordinates, and population by city name in Chinese or English.

Instructions

China city lookup / 中国城市查询 / Chinese cities database / China city tier / 一线二线三线城市 / China prefecture-level city / China city province / China city coordinates / Chinese city info. Look up China city information (name, province, tier, coordinates, population).

Price: unknown on Base (auto-paid in USDC).

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": {
      "name": "<name>"
    },
    "name": "cn402_geo_cn_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCity name in Chinese or English (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided. The description mentions return fields and price (unknown, auto-paid in USDC) but does not disclose case sensitivity or error handling. Some transparency but incomplete.

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

Conciseness2/5

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

Description is cluttered with a redundant keyword list before the main sentence. Not concise; could be streamlined to one clear sentence plus price note.

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

Completeness4/5

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

For a simple lookup with one parameter and no output schema, the description adequately covers input and output fields. Lacks edge case details but still reasonably complete.

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?

Only parameter 'name' has schema description indicating required and Chinese/English. Tool description adds no new semantic value beyond what schema provides, so baseline score of 3.

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 it is for looking up China city information, listing specific fields like name, province, tier, coordinates, population. It distinguishes itself from sibling cn402_geo_cn_province by focusing on cities.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like cn402_geo_cn_province or cn402_geo_distance. No when-not-to-use or context provided.

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