Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

Get FRED Series Data

GetFredSeriesData
Read-onlyIdempotent
    Fetch time-series observation data from FRED for a specific economic
    series. Returns date + value pairs with series metadata (title, units,
    frequency). Use SearchFredSeries first if you don't know the series ID.

    Use this tool when:
    - You need historical macro data (rates, inflation, GDP, unemployment)
    - You want to provide macro context alongside advisor or fund data
    - You are comparing economic conditions across time periods
    - You need the current value of a key economic indicator

    Pass observation_start / observation_end to limit the date range.
    Pass frequency to aggregate (e.g. 'm' for monthly, 'q' for quarterly).

    Requires FRED_API_KEY environment variable (free at fred.stlouisfed.org).
    Source: Federal Reserve Bank of St. Louis FRED API.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"f258bd16-f060-4e4a-a55d-221a0484866d"New value: +"05525087-35e9-4aac-b06d-6d88ce386b2e"
  2. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  3. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  4. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  5. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  6. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  7. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  8. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  9. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  10. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  11. Changed1 schema field changed
    • changedInput schema / $defs / FredSeriesDataParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  12. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotation context: the return shape (date + value pairs with title/units/frequency metadata) and an auth prerequisite (FRED_API_KEY, with where to get it). It does not cover rate limits or pagination behavior.

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?

Front-loads the core action, then routes to the prerequisite tool, then lists trigger scenarios, then parameter usage, then environment requirement. Every sentence carries information; the only mild redundancy is restating the FRED source.

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?

With an output schema present, return values needn't be explained, yet the description still summarizes them. Auth requirement, prerequisite tool, scoping params, and trigger scenarios are all covered — nothing an agent needs to invoke correctly is missing.

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?

The description adds operational meaning for the key FRED parameters — observation_start/observation_end to bound the range and frequency to aggregate (with 'm'/'q' examples) — which the top-level schema does not surface. It does not address the boilerplate-looking params (source_resource_id, wholesaler_ids, exclude_fillers), though those appear unrelated to FRED fetching.

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?

States a specific verb (Fetch) and resource (time-series observation data from FRED) and immediately disambiguates from the sibling SearchFredSeries. An agent can distinguish this from the other ~30 lookup/fetch tools without opening the schema.

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?

Provides an explicit 'Use this tool when' list of scenarios (macro data, advisor/fund context, cross-period comparison, current indicator values) and names the alternative with its condition: 'Use SearchFredSeries first if you don't know the series ID.' Nothing is left to inference.

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.

Resources