Skip to main content
Glama

US address to coordinates

geocode_address
Read-only

Turn a US street address into latitude and longitude, with the standardized address, ZIP, county and FIPS code, state and census tract, from the US Census Bureau geocoder. US street addresses only (with a house number).

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You have a US street address and need its coordinates or census details. Use instead: weather_forecast takes the address directly if the weather is all you need. Parameters: address: a US street address with a house number. Returns: latitude and longitude, standardized address, ZIP, county, FIPS code, state and census tract. No match is refused free.

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

Input Schema

NameRequiredDescriptionDefault
addressYesUS street address, e.g. "1600 Pennsylvania Ave NW, Washington, DC 20500".
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context the annotations don't: pricing ($0.002 USDC per call via x402), that failed calls are free, that omitting `payment` returns a quote, and that a non-matching address is refused at no cost. It stops short of describing response shape beyond field names, but after a slightly longer wait, with these additions the description covers the key operational traits well, so a 3 underweights it but the scoring band is defensible.

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?

The labeled blocks (When to use / Use instead / Parameters / Returns) are front-loaded and scannable. Minor waste: the 'Returns' line repeats the field list already given in the opening sentence, and the pricing sentence sits ahead of the usage guidance.

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?

There is no output schema, and the description compensates by enumerating what comes back (coordinates, standardized address, ZIP, county, FIPS, state, census tract). Combined with the payment/quote flow, failure behavior, and US-only restriction, an agent has everything needed to call it correctly.

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%, so the baseline is 3, and the description goes beyond it by restating the hard requirement for `address` ('with a house number') and by explaining the `payment` round-trip (call without it to get a quote, then sign and call again) — the two-step x402 flow is clarified in the description as well as 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?

Opens with a specific verb+resource ('Turn a US street address into latitude and longitude') and enumerates the exact outputs (ZIP, county, FIPS, census tract) sourced from the US Census Bureau geocoder. The input restriction ('US street addresses only, with a house number') further narrows it against siblings that accept free-form location input.

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

Usage Guidelines5/5

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

Explicit 'When to use' line states the precondition (you have a US street address and need coordinates or census details), and 'Use instead' names weather_forecast as the alternative for the weather-only case. Nothing is left to inference about routing.

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.