us-open-stats-mcp

Get Cbsa Population

get_cbsa_population

Retrieve U.S. Census ACS population estimates for a CBSA by CBSA code and year. Use it to get typed, normalized population snapshots for local statistical analysis.

Instructions

Return ACS population estimate for a CBSA.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cbsa": "<cbsa>"
    },
    "name": "get_cbsa_population"
  }
}

Input Schema

Name	Required	Description	Default
`cbsa`	Yes
`year`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: no indication of data vintage, ACS survey year semantics, rate limits, or that this is a non-mutating lookup. 'ACS' hints at the data source but no operational behavior is described.

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?

A single front-loaded sentence with no filler, which is appropriate sizing for a simple lookup. It is efficient, though the brevity tips into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but with 0% parameter coverage and no annotations the definition leaves the CBSA format and the year parameter undocumented. For a two-parameter tool this is insufficient.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. It never explains the expected CBSA identifier format (e.g., 5-digit FIPS code) and completely ignores the 'year' parameter, which defaults to 2023.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Return) and resource (ACS population estimate) scoped to a CBSA, which is clearly distinct from sibling tools covering unemployment rate, CPI, and FMR. It lacks any explicit contrast with siblings, but the resource itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and names no alternatives. An agent must infer usage entirely from the name and the parameter list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server