Skip to main content
Glama

FinanceQuery

FRED Economic Series

get_fred_series
Read-onlyIdempotent

Get FRED macroeconomic time series data (e.g., FEDFUNDS, CPIAUCSL, GDP, UNRATE). Requires FRED_API_KEY env var.

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": {
      "id": "<id>"
    },
    "name": "get_fred_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFRED series ID (e.g., "FEDFUNDS", "CPIAUCSL", "GDP", "UNRATE")
as_ofNoVintage date (YYYY-MM-DD): the series as it stood then, before later revisions; omitted = latest
limitNoMaximum observations per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds one genuinely useful operational fact — the FRED_API_KEY environment variable requirement — but says nothing about pagination or vintage/revision behavior, both of which materially affect results.

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?

Two short sentences, front-loaded with the resource and followed by the prerequisite. The parenthetical examples duplicate schema content, which is minor padding but not harmful.

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

Completeness3/5

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

For a five-parameter paginated tool with no output schema, the description covers the auth prerequisite and the data domain but omits pagination, observation shape, and revision semantics. The schema carries most of that burden, leaving the description adequate but thin.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (id, as_of, limit, cursor, fields) is already documented precisely, including the vintage and continuation-token semantics. The description adds only repeated example IDs, which the schema already supplies.

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 and resource: retrieve FRED macroeconomic time series, with concrete series IDs as examples. It is distinguishable from market-data siblings like get_indicators or get_analysis by the explicit 'macroeconomic time series' framing, though it never names an alternative.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives such as get_indicators or get_analysis. The agent must infer that this tool is for raw FRED series rather than derived/analytical outputs.

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.