Skip to main content
Glama

US address geocode with Census geographies

geo_us_address
Read-only

Geocodes a one-line US address, or reverse-geocodes a lat/lon point, to coordinates and the Census geographies containing it: state and county FIPS, county subdivision, place, tract, block group, block, ZCTA, congressional and state legislative districts, school districts, urban area, metro or micro area, metro division, CSA, PUMA, census region and division, plus ground elevation in feet. Sources: US Census Geocoder (current benchmark), USGS 3DEP elevation service (EPQS). Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "geo_us_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees for reverse lookup, paired with lon. US states, DC, Puerto Rico and island areas.
lonNoLongitude in decimal degrees for reverse lookup, paired with lat.
addressNoOne-line US street address (5 to 100 characters). Mutually exclusive with lat/lon.
elevationNoInclude USGS ground elevation (default true). The USGS service is slow and can add up to about 7 s to the response; false skips it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / examples
      Previous value: -[
      -  "4201 St Antoine St, Detroit, MI 48201"
      -]New value: +[
      +  "350 5th Ave, New York, NY 10118"
      +]
    • changedInput schema / properties / lat / examples
      Previous value: -[
      -  "42.3514"
      -]New value: +[
      +  "40.7484"
      +]
    • changedInput schema / properties / lon / examples
      Previous value: -[
      -  "-83.0587"
      -]New value: +[
      +  "-73.9857"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses upstream data sources (Census Geocoder current benchmark, USGS 3DEP EPQS) and a concrete price model with the important detail that failed or no-match calls are free. That billing and provenance context is genuinely non-obvious; only the elevation latency caveat sits in the schema rather than the description.

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 core verb phrase, then the output enumeration, then sources and price — a sensible ordering. The long geographies list is justified because there is no output schema, though the single 80+ word sentence is denser than it needs to be.

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?

With no output schema, the description carries the burden of describing returned data and does so thoroughly via the geography enumeration, plus cost and source provenance. It stops short of covering error/ambiguity behavior or the response envelope, which an agent might still want.

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 description coverage is 100%, so the baseline applies; the description adds elevation in feet as a returned field but no additional syntax, format, or constraint detail for address/lat/lon/elevation beyond what the schema already documents.

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 specific verbs (geocodes / reverse-geocodes), a concrete resource (one-line US address or lat/lon point), and enumerates exactly what the caller gets back. The dual forward/reverse mode plus the US-only scope makes it distinguishable at a glance from unrelated siblings like geo_weather.

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?

The description makes the two call modes and their input shapes explicit (address string vs. lat/lon pair), and the schema reinforces mutual exclusivity. It does not, however, say when to prefer this over another tool or what happens for non-US / ambiguous inputs, so there is no true exclusion guidance.

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