Skip to main content
Glama

X420 agent services

x420_geo_geocode

Read-onlyIdempotent

Geocode US address: Street address → coordinates and parsed components using the US Census Bureau Geocoder (free, no key). Source: US Census Bureau. US addresses only; street-segment interpolation, not rooftop. 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: match_count, matches[{matched_address, lat, lon, components}].

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

Input Schema

NameRequiredDescriptionDefault
addressYesone-line US address, e.g. 100 Main St, Arlington, TX 76010

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses behavior that annotations cannot: cost of $0.03 USDC per call, that this hosted instance does NOT return the deliverable but only payment instructions, and the exact 402/x402 retry protocol. That is precisely the non-obvious context an agent needs to avoid treating the response as geocode data.

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?

Purpose, scope, cost and workflow are front-loaded and logically ordered, and the deliverable shape is stated last where it belongs. The legal disclaimer clause ('Not professional, legal, insurance... advice') is boilerplate that adds little for an agent and slightly dilutes an otherwise dense, well-structured description.

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?

For a paid, payment-gated single-input tool with no output schema, the description covers everything needed: input constraints, cost, why no deliverable comes back, how to complete payment, and the shape of the eventual JSON result. No output schema exists, and the description compensates by describing the return fields.

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?

Only one parameter with 100% schema coverage, so baseline is 4. The description adds a real constraint beyond the schema: the address must be a US address, and the format is a single line. That is useful added meaning, though nothing new on the example already present in the schema.

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 ('Geocode US address: Street address → coordinates and parsed components') plus the provider (US Census Bureau Geocoder) and the precision model (street-segment interpolation, not rooftop). The 'US addresses only' scope cleanly separates it from the reverse-geocode sibling.

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 explicit boundaries — US addresses only, interpolation rather than rooftop accuracy, and a full description of the payment-gated usage path (hosted vs. local server with own wallet key). It does not name reverse-geocode as the alternative for the opposite direction, so routing is implied rather than stated.

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