Skip to main content
Glama

Geocode a US address

geocode_address
Read-onlyIdempotent

Turn a US street address into lat/lng plus the normalized address, using the US Census geocoder. The returned lat/lng can be passed to fetch_location, fetch_batch, proximity or parcel_enrich, which also accept the address directly and geocode it the same way. Output: lat, lng, normalized_address, accuracy (1 for a single match, lower when several candidates matched), accuracy_type and precision_note. Points are placed along the street from the house-number range, not on the rooftop, so they can be off on large rural lots. Cost: Free (0 lookups), up to 10,000 geocodes per key per day. Behavior: read-only (no side effects); needs an API key or OAuth; each call counts toward the per-minute request limit (Free 10, Starter 60, Pro 300). Works with an empty balance; each call queries the Census geocoder live with a 30 s timeout, and the 10,000 per day cap resets at 00:00 UTC. Errors: address_not_found when nothing matches, daily_cap_reached (resets 00:00 UTC), upstream_unavailable (retryable).

Input Schema

NameRequiredDescriptionDefault
addressYesUS street address with house number, street, city and state (e.g. '350 5th Ave, New York, NY 10118'). PO boxes and a bare city or ZIP do not geocode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description provides extensive context beyond the standard annotations, including operational details like cost, rate limits (daily/per minute), time limits (30s timeout), required authentication (API key), specific behavioral quirks (points placed along the street), and detailed error handling.

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?

Despite its length, the definition is perfectly structured. Every complex detail—usage, cost, behavior, errors—is front-loaded and highly efficient, earning its place through its high information density.

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?

It is complete. It defines the expected output fields (`lat`, `lng`, `normalized_address`, `accuracy`, etc.) and covers all operational aspects (limits, errors, behavior) that an agent would need to decide whether to call the tool successfully.

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?

While schema coverage is 100%, the description adds critical semantic constraints, explicitly defining required format components (number, street, city, state, ZIP) and stating what is invalid (PO boxes, bare ZIP).

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?

The description immediately identifies the specific action (Turn address into lat/lng) and resource (US street address) and clearly distinguishes its scope and purpose from related fetching and batch tools.

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?

It provides direct routing advice, stating that the resulting lat/lng can be passed to several downstream tools (`fetch_location`, `proximity`, etc.), but also clarifies that these tools can handle the address directly as an alternative.

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