Skip to main content
Glama

Census Geocoding Tool

geocoding_tool
Read-onlyIdempotent

Convert addresses to latitude/longitude coordinates and retrieve Census geographic hierarchies including state, county, tract, and block. Supports forward and reverse geocoding without requiring an API key.

Instructions

Convert addresses to coordinates or find Census geographies for an address/location. Returns latitude/longitude coordinates and all Census geographic hierarchies (state, county, tract, block, MSA, congressional district, etc.). Supports forward geocoding (address to coordinates) and reverse geocoding (coordinates to geographies). No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTypeNoSearch type: "onelineaddress" (single line address), "address" (structured address), "coordinates" (reverse geocoding)onelineaddress
addressNoSingle line address (e.g., "1600 Pennsylvania Avenue NW, Washington, DC 20500"). Required for onelineaddress search.
streetNoStreet address (required for address search)
cityNoCity name
stateNoState (2-letter code or full name)
zipNoZIP code
longitudeNoLongitude (required for coordinates search)
latitudeNoLatitude (required for coordinates search)
returnGeographiesNoReturn geographic hierarchies (state, county, tract, block, MSA, etc.) in addition to coordinates
benchmarkNoBenchmark version (default: Public_AR_Current for current data)Public_AR_Current
vintageNoGeography vintage (default: Current_Current for current boundaries). Only used when returnGeographies is true.Current_Current

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds context by noting no API key required and detailing the output (coordinates and geographic hierarchies). No contradictions.

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?

The description is concise, front-loaded with the main purpose, and every sentence adds essential information without fluff.

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?

Given the high schema coverage, existence of an output schema, and rich annotations, the description adequately covers the tool's functionality, including both geocoding modes and the return of geographic hierarchies.

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?

The input schema covers all parameters with descriptions (100% coverage). The description adds value by explaining the two search types but does not significantly expand on parameter meaning beyond 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?

The description clearly states the tool converts addresses to coordinates or finds Census geographies, and specifies forward and reverse geocoding. It distinguishes itself from sibling tools by emphasizing Census geographic hierarchies.

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 explains the two search types and notes that no API key is required. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattpodwysocki/census-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server