Skip to main content
Glama
mcpwright
by mcpwright

Get housing by ZIP

get_housing
Read-only

Retrieve housing metrics for a U.S. ZIP code: median home value, monthly rent, occupied units, and owner-occupied share. Uses ACS 5-year data; values capped at $2,000,001.

Instructions

Housing measures for a ZIP: home value, rent, and owner-occupied share.

`zip_code`: a 5-digit US ZIP. Returns the median value of owner-occupied
homes, the median gross rent (monthly), the number of occupied housing
units, and the percent that are owner-occupied — all ACS 5-year estimates.
Note: ACS top-codes median home value at $2,000,001, so the priciest ZIPs
(e.g. Atherton 94027) report exactly that — read it as "$2M or more," not an
exact value.

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)
occupied_unitsNoTotal occupied housing units
median_gross_rentNoMedian gross rent (rent + utilities), monthly
median_home_valueNoMedian value of owner-occupied homes
owner_occupied_pctNoPercent of occupied units that are owner-occupied (0-100)
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral details: it returns ACS 5-year estimates and calls out the top-coding caveat for median home value at $2,000,001, explaining that values like Atherton's 94027 represent '$2M or more' rather than exact figures. This adds significant interpretive context.

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 compact and well-structured, around 100 words across three sentences plus a note. Every sentence contributes: the first introduces the metrics, the second defines the input and return fields, and the third adds a crucial caveat. No filler or redundancy.

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 output schema exists, the description need not restate return formats. It covers the essential context: data source (ACS 5-year), the specific variables, and a critical interpretation warning. This is complete for a single-ZIP housing data tool with strong annotations and an output schema.

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 schema only labels zip_code as 'Zip Code' with type string (0% schema description coverage). The description compensates fully by stating that zip_code is a 5-digit US ZIP and providing an example (Atherton 94027) within a realistic context, giving the agent precise format and usage guidance.

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?

Description clearly identifies the tool as providing housing measures for a ZIP, specifically home value, rent, and owner-occupied share. This distinguishes it from sibling tools like get_income or get_demographics by naming the exact metrics returned.

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 conveys a clear context for use — 'Housing measures for a ZIP' — and enumerates the variables, making it obvious when this tool is appropriate. It does not explicitly exclude alternatives or name sibling tools, but the context is strong enough to guide selection.

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