Skip to main content
Glama

X420 agent services

x420_geo_reverse-geocode

Read-onlyIdempotent

Reverse geocode (US geographies): Coordinates → state, county, place, metro area, census tract and block GEOIDs from the US Census Bureau Geocoder (free, no key). Source: US Census Bureau. Returns administrative geographies, not a street address; US only. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.03 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: in_us, state{name,fips,usps}, county, place, combined_statistical_area, urban_area, tract_geoid, block_geoid.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "x420_geo_reverse-geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld/non-destructive) by disclosing the critical behavioral fact that this hosted tool 'does NOT pay and does NOT return the deliverable' and instead only validates input and returns payment instructions. It adds pricing ($0.03 USDC on Base via x402), the free/no-key upstream source, and an explicit scope disclaimer, so an agent knows exactly what it will and will not get back.

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

Conciseness4/5

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

Front-loaded with purpose and output fields before the payment mechanics, so the most important information comes first. It is dense but every clause carries operational weight (US-only bound, non-delivery warning, payment retry flow); the only near-filler is the standard 'not professional, legal... advice' disclaimer.

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

Completeness5/5

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

With no output schema, the description compensates by listing the exact deliverable keys (in_us, state{name,fips,usps}, county, place, combined_statistical_area, urban_area, tract_geoid, block_geoid). It also resolves the biggest ambiguity for a paid tool — that the call returns payment instructions rather than data — and gives the full pay-and-retry procedure.

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% and both lat/lon are documented in the schema, so the schema carries the parameter burden. The description adds only a directional mapping ('Coordinates →') between inputs and outputs, not format detail such as decimal degrees vs. strings or precision expectations. Baseline 3 applies.

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?

States a specific verb and resource ('Reverse geocode (US geographies): Coordinates → state, county, place, metro area, census tract and block GEOIDs') and pins the exact source (US Census Bureau Geocoder). It also implicitly distinguishes itself from the forward-geocoding sibling by naming the input direction and the returned geography types.

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

Usage Guidelines4/5

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

Gives clear usage boundaries: 'US only' and 'Returns administrative geographies, not a street address', which steers an agent away when a street address is needed. It also spells out the invocation sequence (GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE) and the alternative path (local x420-mcp server with own wallet). It stops short of naming x420_geo_geocode as the inverse tool explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources