BEA Economic Accounts

get_county_employment

Get total full-time and part-time employment by county from BEA (CAEMP25N table).

Returns employment counts 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

TDQS

A4.6/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 discloses that omitting year returns last 5 years and specifies the data source (BEA table). It does not mention whether the operation is read-only or any potential side effects, but the nature of 'get' implies read-only. No contradictions.

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?

The description is concise and well-structured: a clear one-sentence summary, followed by a behavioral note, format specification, and an Args section. Every sentence is informative with no redundancy.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no nested objects) and the presence of an output schema, the description sufficiently covers what the tool returns (employment counts) and the data source. It is complete for effective usage.

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%, so the description fully explains both parameters: county_fips format with examples (e.g., '53067' for county, '53000' for state total) and year with default behavior (last 5 years if omitted). This adds significant value beyond 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 the tool retrieves total full-time and part-time employment by county from BEA (CAEMP25N table). It specifies the resource (county employment) and the action (get), and the sibling tools (e.g., get_county_gdp) help distinguish it from other economic data tools.

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?

The description explains when to use the tool (for county or state employment data) and gives format examples for GeoFips. It does not explicitly state when not to use it or provide alternative tools, but the sibling list provides context. The omission of year returns last 5 years is a clear guideline.

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?