Skip to main content
Glama

Geocodes a one-line US address with the US Census Bureau

us_geocode
Read-only

Geocodes a one-line US address with the US Census Bureau: matched address, coordinates, county, state, census tract and block group. Addresses that do not match answer 404 (not charged). Public domain data. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "us_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesOne line, US address

Output Schema

NameRequiredDescriptionDefault
latNo
lonNo
queryNo
stateNo
countyNo
sourceNo
checkedAtNo
stateFipsNo
blockGroupNo
countyFipsNo
attributionNo
censusTractNo
matchedAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful beyond-schema behavior: the 404-on-no-match contract, that failures are not billed, the data licensing (public domain), and the x402 payment mechanism across named networks.

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

Conciseness5/5

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

Two dense sentences, front-loaded with the action and return fields, then pricing and failure semantics. No filler and nothing repeated from structured fields in a wasteful way.

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?

An output schema exists, so field-level return documentation is not required, and the description still names the key outputs. Pricing, failure behavior, and coverage are all present; the only minor gap is explicit comparison against the generic geocode sibling.

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?

Only one parameter and schema coverage is 100%, with the schema itself saying 'One line, US address'. The description restates the one-line US format but adds no formatting rules, examples, or parsing caveats beyond what the schema already provides, so 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 (geocodes), a specific resource (one-line US address), and the authoritative source (US Census Bureau), plus enumerates the returned fields. The 'US' scoping distinguishes it from a general geocode sibling without needing the sibling's schema.

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

Usage Guidelines3/5

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

Agencies get clear conditional behavior (non-matching addresses return 404 and are not charged) and cost per successful call, which informs when to call it. However, there is no explicit routing guidance such as 'use geocode instead for non-US addresses', so the alternative is only implied by the 'US' qualifier.

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