Skip to main content
Glama

x420_geo_reverse-geocode

Convert US latitude/longitude coordinates into state, county, place, metro area, census tract, and block GEOIDs via Census Bureau data; returns administrative geographies, not street addresses.

Instructions

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. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: in_us, state{name,fips,usps}, county, place, combined_statistical_area, urban_area, tract_geoid, block_geoid - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081"}.

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 observedv1.0.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description adds substantially more: a real-money cost of $0.03 USDC per call on Base via x402, the required X420_MCP_WALLET_PRIVATE_KEY wallet, the upstream source (US Census Bureau, no key), and that the response includes a signed receipt and settlement transaction. That tells the agent this is a metered, non-free call and what side artifacts come back.

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

Conciseness3/5

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

Front-loaded and well ordered (what it does, scope, cost, returns, example), but it contains waste: the source is stated twice ("from the US Census Bureau Geocoder" and "Source: US Census Bureau") and the legal/medical/financial disclaimer sentence is boilerplate that does not help tool selection or invocation.

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 still lists the returned fields (in_us, state{name,fips,usps}, county, place, combined_statistical_area, urban_area, tract_geoid, block_geoid), plus payment mechanics and geographic scope. For a paid, single-purpose lookup this is enough for an agent to call it correctly and anticipate the cost and response shape.

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% (both lat and lon documented as strings), so the schema already carries the baseline. The description adds a concrete example input {"lat":"32.7357","lon":"-97.1081"}, clarifying that the values are string-encoded signed decimals — useful detail the schema does not convey.

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 ... Coordinates → state, county, place, metro area, census tract and block GEOIDs") and enumerates the exact outputs. The word "Reverse" plus the coordinate-input framing cleanly separates it from the forward-geocode sibling x420_geo_geocode without needing to open either schema.

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 selection context: input is coordinates, coverage is "US only", and it explicitly warns it "Returns administrative geographies, not a street address", which steers an agent away from using it for address resolution. It stops short of naming the sibling to use instead for address→coordinate lookups, so routing is implied rather than explicit.

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