BEA Economic Accounts

get_county_gdp

Get GDP by county from the BEA Regional accounts (CAGDP1 table).

Returns all-industry GDP 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' for Thurston County, WA).
For state totals use 2-digit state FIPS + '000' (e.g. '53000' for Washington).

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

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It explains data source, return behavior (last 5 years if year omitted), and FIPS format. Lacks details on permissions, rate limits, or error handling, but covers core behavior well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with a clear lead sentence, bullet-like Args section, and no redundant text. Every sentence adds value, and the length is appropriate for the tool's complexity.

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 the presence of an output schema (though not shown), the description adequately covers input and behavioral aspects. It does not discuss error cases or data lag, but for a simple get tool, it is reasonably complete.

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?

Schema coverage is 0%, but description compensates by explaining the format of county_fips (including state total example) and the effect of omitting year. This adds significant meaning beyond the bare 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 it retrieves GDP by county from the BEA Regional accounts (CAGDP1 table), which is a specific resource and action. It distinguishes from sibling tools like get_county_employment and get_metro_gdp by focusing on GDP data.

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 for when to use (county or state total GDP) and behavior when year is omitted. Does not explicitly state when not to use or list alternatives, but sibling names offer implicit guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_county_employment, get_county_gdp, get_county_personal_income, get_metro_gdp, and list_available_tables all target different economic metrics or discovery. There is no overlap or ambiguity.

Naming Consistency4/5

Tools consistently use the verb_noun pattern with get_ for data retrieval and list_ for discovery. The minor deviation of list_available_tables instead of get_available_tables is acceptable and does not cause confusion.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of providing regional economic data. Each tool serves a specific need without unnecessary bloat or deficiency.

Completeness3/5

The server covers key county-level indicators and metro GDP, but lacks tools to retrieve data from other tables discovered via list_available_tables. This is a notable gap, though the discovery tool partially mitigates it.

Resources

Need Help?