Skip to main content
Glama

Census Population

census_population
Read-onlyIdempotent

HOW MANY PEOPLE LIVE somewhere in the United States, the population of a county, city, town, ZIP code or state from the American Community Survey. Answers "population of Travis County Texas", "how many people live in Austin", "what is the population of 78701", "Ohio population". Say the place the way a person says it ("Travis County, TX", "Austin, TX", "78701", "Texas"); no FIPS codes and no variable codes needed. Also returns median age, household count and median household income for the same place when the survey publishes them. Figures are 5-year survey estimates, so they describe a period rather than a census-day headcount. For what homes cost or rent there, use census_acs.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place": "Travis County, TX"
    },
    "name": "census_population"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoACS 5-year survey year (default 2022; available from 2009).
placeYesThe place, in plain English: "Travis County, TX", "Austin, TX", "78701", "Texas". A county or place name works best with its state.
_apiKeyNoCensus API key

Output Schema

NameRequiredDescriptionDefault
yearYes
foundYes
placeYes
sourceYes
householdsNo
median_ageNo
populationYes
estimate_noteNo
median_household_income_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description still adds real value beyond them: the figures are 5-year survey estimates describing a period rather than a census-day headcount, no FIPS or variable codes are required, and median age, household count and median household income come back alongside population. It does not mention rate limits or failure behavior for unmatched places, which keeps it off a 5.

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 population question is front-loaded in the first sentence and the caveats follow in a logical order (formatting, extra returns, estimate vintage, alternative tool). The all-caps opening and "Say the place the way a person says it" phrasing are slightly informal, but no sentence is wasted.

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?

Output schema and annotations exist, so the description needn't explain return structure or safety. It covers the remaining gaps an agent needs: data vintage (ACS 5-year estimates), input affordances (plain-English place names, no codes), and the boundary with census_acs.

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?

Schema coverage is 100% and the schema already supplies the place-format examples ("Travis County, TX", "Austin, TX", "78701", "Texas") and the year default/range. The description reinforces this by stating no FIPS or variable codes are needed and that a county/place name works best with its state, but that largely restates the schema — baseline 3 is appropriate.

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 names a specific question class ("HOW MANY PEOPLE LIVE", "population of a county, city, town, ZIP code or state") and the data source (American Community Survey). It also distinguishes itself from the sibling census_acs by routing cost/rent questions there, so an agent can tell the two apart without opening a schema.

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 gives concrete example phrasings that trigger the tool ("population of Travis County Texas", "Ohio population") and explicitly names the alternative for a related but out-of-scope need ("For what homes cost or rent there, use census_acs"). That is a clear when-to-use plus an exclusion, not just implied context.

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.