Skip to main content
Glama
mcpwright
by mcpwright

Get income by ZIP

get_income
Read-only

Retrieve income metrics for a U.S. ZIP code: median household income, per-capita income, household count, and percentage earning $200k+ based on ACS 5-year estimates.

Instructions

Income measures for a ZIP: median household, per-capita, and % $200k+.

`zip_code`: a 5-digit US ZIP. Returns median household income, per-capita
income, the number of households, and the percent of households earning
$200k+ — all ACS 5-year estimates in USD. Note: ACS top-codes median
household income at $250,001, so the wealthiest ZIPs (e.g. Atherton 94027)
report exactly that — read it as "$250k or more," not an exact figure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCensus name for the area
zctaYes5-digit ZIP Code Tabulation Area
vintageYesACS 5-year data vintage (end year)
total_householdsNoTotal number of households
per_capita_incomeNoPer-capita income
median_household_incomeNoMedian household income
households_200k_plus_pctNoPercent of households with income $200k+ (0-100)
Behavior5/5

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

The description discloses the ACS top-coding limit ($250,001) and explains how to interpret the result for wealthy ZIPs, which is critical behavioral context beyond the readOnlyHint and openWorldHint annotations. It also specifies data source and units, adding meaningful transparency.

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 front-loaded with the core purpose, followed by a concise parameter explanation and a crucial caveat. Every sentence adds value, with no redundancy or padding.

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?

The tool is simple (single parameter, no enums), and the description covers the data source, the top-coding nuance, and the parameter format. The presence of an output schema handles return values, so the description is complete for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides no description for zip_code, but the description fully compensates by explicitly defining it as a 5-digit US ZIP and connecting it to the returned metrics. This is a clear, complete explanation of the parameter's meaning.

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 provides ZIP-level income measures, enumerating median household income, per-capita income, and % $200k+. It differentiates itself from siblings by focusing specifically on income, not demographics or housing.

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?

The description implies use for income data but does not explicitly compare with alternatives like get_demographics or compare_zips. It lacks clear 'when to use' or 'when not to use' statements, leaving guidance implied rather than directly stated.

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/mcpwright/census-mcp'

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