Census ACS Demographics
Server Details
Population, income, poverty, education, housing, and commuting from the US Census ACS
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 5 of 5 tools scored.
Each tool has a clearly distinct purpose targeting specific demographic domains: commuting, general demographics, economics, education, and flexible tract-level data. The descriptions clearly differentiate the data categories returned, with no overlap that would cause confusion. An agent can easily select the right tool based on the specific data needed.
All tools follow a consistent verb_noun pattern with 'get_' prefix followed by the data domain (e.g., get_commuting_data, get_county_demographics). The naming is perfectly predictable and follows the same snake_case convention throughout. This consistency makes the tool set easy to navigate and understand.
Five tools is well-scoped for a demographic data server, covering key ACS domains (commuting, demographics, economics, education) plus a flexible query tool. Each tool earns its place by addressing distinct data needs without redundancy. The count is neither too thin nor bloated, fitting the server's purpose perfectly.
The tool set provides strong coverage of core ACS domains with dedicated tools for major categories and a flexible tool for custom queries. Minor gaps exist, such as no dedicated tool for housing characteristics or employment data beyond commuting, but the flexible get_tract_data can fill these gaps. Overall, the surface supports most common demographic analysis workflows effectively.
Available Tools
5 toolsget_commuting_dataInspect
Get means of transportation to work data for counties.
Returns worker counts and percentages for: drove alone, carpooled,
public transit, walked, bicycle, taxi/motorcycle/other, and worked from home.
Args:
state: Two-letter state abbreviation (e.g. 'WA', 'CA') or 2-digit FIPS code.
county_fips: Three-digit county FIPS code (e.g. '033' for King County).
Omit to get all counties in the state.
year: ACS 5-year estimate year (default 2022).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes | ||
| county_fips | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_county_demographicsInspect
Get demographic data for counties: population, median age, race, Hispanic origin, income, and poverty.
Returns one record per county with total population, median age, racial breakdown
(White, Black, American Indian, Asian, Pacific Islander, Other, Two+),
Hispanic/Latino percentage, median household income, and poverty rate.
Args:
state: Two-letter state abbreviation (e.g. 'WA', 'CA') or 2-digit FIPS code.
county_fips: Three-digit county FIPS code (e.g. '033' for King County).
Omit to get all counties in the state.
year: ACS 5-year estimate year (default 2022). Data covers year-4 through year.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes | ||
| county_fips | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_county_economicsInspect
Get economic data for counties: income, poverty, home values, rent, and health insurance.
Returns median household income, poverty rate, median home value, median gross rent,
and health insurance coverage rates (insured vs uninsured).
Args:
state: Two-letter state abbreviation (e.g. 'WA', 'CA') or 2-digit FIPS code.
county_fips: Three-digit county FIPS code (e.g. '033' for King County).
Omit to get all counties in the state.
year: ACS 5-year estimate year (default 2022).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes | ||
| county_fips | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_county_educationInspect
Get educational attainment for counties (population 25+).
Returns counts and percentages for: less than high school, high school diploma/GED,
some college/associate degree, bachelor's degree, and graduate/professional degree.
Args:
state: Two-letter state abbreviation (e.g. 'WA', 'CA') or 2-digit FIPS code.
county_fips: Three-digit county FIPS code (e.g. '033' for King County).
Omit to get all counties in the state.
year: ACS 5-year estimate year (default 2022).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes | ||
| county_fips | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_tract_dataInspect
Get tract-level ACS data for any variables within a county.
This is a flexible tool for querying any ACS 5-year estimate variables at
the census tract level. Automatically batches requests if more than 50
variables are requested.
Common variable examples:
- B01001_001E: Total population
- B19013_001E: Median household income
- B17001_002E: Population below poverty level
- B25077_001E: Median home value
- B02001_002E-008E: Race breakdown
Args:
state: Two-letter state abbreviation (e.g. 'WA') or 2-digit FIPS code.
county_fips: Three-digit county FIPS code (e.g. '033' for King County, WA).
variables: Comma-separated ACS variable codes (e.g. 'B01001_001E,B19013_001E').
NAME is always included automatically.
year: ACS 5-year estimate year (default 2022).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| state | Yes | ||
| variables | Yes | ||
| county_fips | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!