Skip to main content
Glama

x420_geo_geocode

Convert a one-line US street address into latitude/longitude coordinates and parsed address components via the US Census Bureau Geocoder.

Instructions

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. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: match_count, matches[{matched_address, lat, lon, components}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"address":"1600 Pennsylvania Ave NW, Washington, DC 20500"}.

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

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false; the description adds substantial context beyond them — $0.03 USDC per call, x402 settlement on Base from X420_MCP_WALLET_PRIVATE_KEY, plus accuracy and liability caveats. The apparent tension between "free, no key" and "PAID" is resolvable (the Census source is free, the wrapper costs money) but could be phrased less ambiguously.

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 the action and source, then pricing and return shape, which is the right order for an agent deciding whether to call. However, "Source: US Census Bureau" repeats the engine already named, and the standard legal disclaimer is boilerplate that dilutes the payload.

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, single-parameter tool with no output schema, the description supplies cost, payment mechanism, output shape (match_count, matches with matched_address/lat/lon/components), and accuracy expectations. An agent has everything needed to decide and invoke correctly.

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?

With a single parameter at 100% schema coverage and an example already present in the schema, the schema carries the burden. The description's extra "Example input" mirrors the schema example, so it adds little new meaning about address formatting or normalization.

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 exact engine (US Census Bureau Geocoder). The "US addresses only" restriction and the forward-geocoding direction also separate it from the reverse-geocode sibling without naming it.

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 qualifying conditions: US addresses only, and it is not rooftop-accurate (street-segment interpolation). It does not explicitly say when to prefer a sibling such as reverse-geocode, so it falls short of full alternative routing.

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