Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

fred_series_data

Read-onlyIdempotent

Retrieve historical observations for any FRED economic series, such as GDP, unemployment, or interest rates, with customizable date ranges and frequencies.

Instructions

Get observations for a FRED series. Popular: GDP, UNRATE, CPIAUCSL, FEDFUNDS, DGS10, MORTGAGE30US

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax obs (default 1000)
end_dateNoYYYY-MM-DD
frequencyNod=daily, w=weekly, bw=biweekly, m=monthly, q=quarterly, sa=semiannual, a=annual
series_idYesSeries ID
sort_orderNodefault: desc
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2026.9.14
    • changedInput schema / properties / frequency / description
      Previous value: -"d, w, bw, m, q, sa, a"New value: +"d=daily, w=weekly, bw=biweekly, m=monthly, q=quarterly, sa=semiannual, a=annual"
    • addedInput schema / properties / frequency / enum
      Added value: +[
+  "d",
+  "w",
+  "bw",
+  "m",
+  "q",
+  "sa",
+  "a"
+]
    • addedInput schema / properties / limit / default
      Added value: +1000
  2. Changed1 schema field changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2026.3.9

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds popular series IDs but not behavioral details such as default limit, date-range filtering, or output shape; no contradiction exists.

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 with no filler; the purpose is front-loaded. The popular-series list is useful but not essential, keeping it just below a top score.

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 read-only fetch tool, the schema and annotations cover parameters and safety adequately. However, there is no output schema and no description of the return shape or when to prefer this over related FRED tools, leaving moderate gaps.

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%, with all parameters described including enums for frequency and sort_order. The description does not add parameter semantics beyond naming example series_id values, so the baseline of 3 applies.

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: 'Get observations for a FRED series.' This is clear and distinguishable from sibling tools like fred_search and fred_series_info, though it does not explicitly name those alternatives.

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?

No guidance on when to use this tool versus fred_search, fred_series_info, or fred_release_data. The list of popular series hints at common usage but does not state conditions, exclusions, or alternatives.

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

Deploy Server

Other Tools