fred-mcp-server

fred_releases

Retrieve all FRED economic data releases. Filter by date, limit, offset, and sort order to find specific releases.

Instructions

Get all FRED releases of economic data.

Returns: dict with key 'releases'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`realtime_start`	No
`realtime_end`	No
`limit`	No
`offset`	No
`order_by`	No
`sort_order`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2May 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It only states the tool 'gets' data (implied read), but does not disclose any behavioral traits such as pagination, default limits, or whether it returns all releases without filtering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (two sentences) and front-loaded with the purpose. However, it is under-specified, sacrificing necessary information for brevity.

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

Completeness2/5

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

Given the extensive set of sibling tools and the complexity of the FRED API, the description fails to provide contextual completeness. It does not define what a 'release' is, how parameters affect results, or what the output schema contains.

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

Parameters1/5

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

Schema description coverage is 0%, but the description provides no explanation for any of the 6 parameters (e.g., realtime_start, limit, order_by). The agent must infer meaning solely from schema names and types, which is insufficient.

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's action ('Get all FRED releases') and the resource ('of economic data'), which is specific and distinguishes it from siblings like fred_release (single release) or fred_release_series (series of a release).

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 is provided on when to use this tool versus the many similar sibling tools (e.g., fred_release, fred_releases_dates). The agent receives no context about selection criteria.

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