Query U.S. Census Bureau data, variables, and geography via MCP. STDIO or Streamable HTTP.
Five read-only Census API tools with comprehensive, well-structured schemas and detailed descriptions. All tools have explicit input schemas with typed parameters and clear descriptions (avg 250+ chars). Tool names follow verb_noun pattern (census_compare_geographies, census_get_variable, etc.). Descriptions are LLM-optimized, explaining WHAT the tool does, WHEN to use it, and key prerequisites. Output schemas are documented implicitly through parameter descriptions. No destructive operations, so error handling focuses on validation and recovery guidance. Main gaps: no explicit output schema documentation in source, no per-tool error classification, and parameter descriptions could include more format/constraint examples (e.g., 'FIPS codes are 2-5 digit strings').
Compare one or more variables across multiple geographies at the same level — all counties in a state, all states nationally, or a named set of specific geographies. Results are sorted and ranked. Covers queries like "rank states by poverty rate", "compare median income across WA counties", or "which census tracts in King County have the highest renter rate." Omit within to compare all geographies nationally at the level. Suppressed values are decoded to human-readable labels rather than passed through as raw negative sentinels. On the business datasets (cbp, ecnbasic, nonemp), pep/charv, and dec/ddhca, use predicates to rank within one industry, size class, or population group — a comparison that omits one ranks on a default the Census API picks, which is an all-categories total on some dimensions and a single category on others. Each row names the defaults that were applied in applied_filters, and census_list_predicate_values enumerates the codes a dimension accepts. A dataset that publishes several records per geography cannot be ranked until one is pinned: pep/charv publishes an April estimates base and a July estimate, so a comparison that pins neither fails with ambiguous_rows rather than giving every geography two ranks — pass predicates {"MONTH": "7"} for the July estimate.
Fetch full metadata for one or more Census variable codes — label, concept group, predicate type, universe, and margin-of-error sibling references. Use to confirm a variable code before building a query, or to look up what a known code means. On ACS datasets it returns estimate_code and moe_code sibling references so you can request both without a separate search; other dataset families publish no margins of error and carry neither field. It also resolves predicate codes such as NAICS2017 or SEX, confirming a filter dimension exists in a dataset before a query uses it — for the values a dimension accepts rather than the dimension itself, call census_list_predicate_values.
Output schemas not explicitly documented in source code. While parameter descriptions are thorough, return types and field structures are inferred rather than formally declared.
Parameter descriptions lack explicit format constraints and examples. E.g., 'State FIPS' should specify '2-digit numeric string (01-56)' and 'within parameter accepts state FIPS like "53" for WA or "*" for all states'.
No explicit error classification or recovery guidance in tool descriptions. Tools should document common failure modes (e.g., 'ambiguous_rows' for pep/charv without MONTH predicate) and suggest recovery steps.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Browse available Census Bureau datasets with their supported vintage years. Use as the starting point when the right dataset is unknown — ACS5, ACS1, population estimates, decennial census, and the business datasets (County Business Patterns, Economic Census, Nonemployer Statistics) serve different use cases. Pass the dataset_id value to the dataset parameter in other census tools. Each description names the predicates a dataset requires and the geography levels it publishes, both of which vary by dataset.
List the geography levels available for a given Census dataset and year, along with the parent geographies each level requires. Use before querying to confirm that the target geography level exists — ACS1 omits many sub-state levels, and not all datasets support tracts or block groups. The geography_level values returned here are the valid inputs to the geography_level parameter in census_query_data and census_compare_geographies.
List the codes a Census filter dimension accepts, so a predicates map can be written without guessing. Answers the question left open when census_query_data or census_compare_geographies reports that a dimension was left unset. Which route a dimension takes depends on the vintage: NAICS and POPGROUP always publish a value list in the dataset dictionary, and on the current vintages EMPSZES, LFO, RCPSZES, TAXSTAT, and TYPOP publish none and are enumerated here against the live data endpoint instead. A dictionary value list is a classification shared across Census products rather than a list of what one dataset serves, and roughly half of its codes typically return no rows anywhere — those are checked against the dataset's own published rows and dropped, and the response source field says whether that check ran. The dictionary lists run to thousands of codes and are best narrowed with query. Pass the returned code as the dimension's value in predicates.
census_list_predicate_values has complex conditional logic (within_naics only applies to certain dimensions) that is documented but could be clearer with explicit mutual-exclusivity notes.
No pagination guidance in tool descriptions. Tools like census_list_predicate_values accept 'limit' but do not document default behavior when results exceed limit or how to iterate.