Skip to main content
Glama

Bea Gov Get Data

bea_gov_get_data
Read-onlyIdempotent

Fetch actual BEA economic data from the specified dataset (e.g. NIPA) using dataset-specific parameters; returns time series values such as GDP, PCE, regional income, and GDP by industry — US ONLY, and only when you already know the dataset-specific parameters (call parameter_list first). GDPbyIndustry additionally requires Industry and Frequency codes this tool cannot guess from a plain-English question. For "what share of GDP comes from " or "'s agriculture share of GDP" trended over time, prefer worldbank's get_indicator (NV.AGR.TOTL.ZS for agriculture) — it needs only a country code and works for any country, not just the US.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "NIPA"
    },
    "name": "bea_gov_get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetYes

Output Schema

NameRequiredDescriptionDefault
BEAAPINoBEA API response wrapper

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description adds non-obvious behavior: the tool cannot infer dataset-specific codes and will fail without them, and the result set is restricted to US data. It does not discuss rate limits or error behavior, but the added constraints are substantive.

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?

The core action and the prerequisite are front-loaded in the first clause, and each subsequent clause adds a real constraint or routing rule. It is dense but largely earns its length, though the trailing worldbank comparison is long enough to slightly dilute the main instruction.

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?

With an output schema present, the description need not explain return values, and its coverage of scope, prerequisites, and alternatives is strong for a one-parameter tool. The remaining gap is the mismatch between the described dataset-specific parameter set and the single-parameter schema.

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

Parameters4/5

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

Schema coverage is 0% for the single 'dataset' parameter, so the description must carry the load, and it does by naming concrete valid datasets (NIPA, GDPbyIndustry) and the auxiliary codes each needs. The one gap is that it refers to plural 'dataset-specific parameters' while the schema exposes only 'dataset', leaving the actual call shape slightly ambiguous.

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 opens with a specific verb and resource ('Fetch actual BEA economic data from the specified dataset') and concretely names the return content (GDP, PCE, regional income, GDP by industry). It explicitly distinguishes itself from two alternatives: parameter_list as a prerequisite and worldbank's get_indicator for cross-country share-of-GDP questions.

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

Usage Guidelines5/5

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

It states hard preconditions ('only when you already know the dataset-specific parameters (call parameter_list first)'), a hard scope limit ('US ONLY'), and a concrete routing rule to a named alternative with the exact indicator code (NV.AGR.TOTL.ZS). It also flags a case the tool cannot handle (guessing Industry/Frequency codes for GDPbyIndustry), so the agent knows when not to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.