BEA Economic Accounts

get_county_personal_income

Get personal income by county from the BEA Regional accounts (CAINC1 table).

Returns total personal income for a county or state total. When year is omitted,
returns the last 5 available years.

GeoFips format: 5-digit county FIPS (e.g. '53067') or state total (e.g. '53000').

Args:
    county_fips: 5-digit county FIPS code (e.g. '53067') or state total (e.g. '53000').
    year: Specific year to retrieve. Omit for last 5 years.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided; description reveals behavior (year omission → last 5 years) and FIPS format, but doesn't cover potential errors, rate limits, or data freshness.

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?

Concise overall, but the 'Args' section slightly duplicates the parameter listing. First sentence is clear and front-loaded.

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

Completeness4/5

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

Given output schema exists, description covers input semantics well. Missing details on data units or error handling, but sufficient for a straightforward data retrieval tool.

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?

With 0% schema description coverage, the description fully compensates by explaining county_fips format with examples and year's default behavior, adding critical context not inferable from the schema.

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 clearly states 'Get personal income by county from the BEA Regional accounts (CAINC1 table)' with specific verb and resource. It distinguishes from siblings (employment, GDP) by focusing on personal income.

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?

Provides clear context on omitting year for last 5 years and GeoFips format, but no explicit when-not-to-use or alternatives to siblings.

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

All BEA Economic Accounts tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?