fred-mcp-server

fred_releases_dates

Fetch release dates for all FRED economic releases. Supports real-time period filtering, pagination, sorting, and inclusion of dates without data.

Instructions

Get release dates for all FRED releases.

Args: realtime_start: Start of real-time period (YYYY-MM-DD). realtime_end: End of real-time period (YYYY-MM-DD). limit: Max number of results. offset: Pagination offset. order_by: Sort results by this field. sort_order: "asc" or "desc". include_release_dates_with_no_data: If true, include release dates that have no data.

Returns: dict with key 'release_dates'.

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_dates"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2May 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as data freshness, rate limits, or side effects. It only states the function and parameters, failing to add transparency beyond basic functionality.

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 description is well-structured with a clear front-loaded sentence followed by parameter descriptions. It is concise without unnecessary words, though slightly verbose with full-sentence parameter listings.

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?

For a data retrieval tool with 7 optional parameters and a simple output schema, the description covers the purpose and all parameters. It lacks background context on 'release dates' but is reasonably complete given the 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?

With 0% schema description coverage, the description fully compensates by explaining each parameter (e.g., 'realtime_start: Start of real-time period (YYYY-MM-DD).'). These explanations add meaningful context beyond the schema's type-only definitions.

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?

The description clearly states 'Get release dates for all FRED releases,' specifying the verb and resource. It implicitly differentiates from sibling 'fred_release_dates' by including 'all,' but does not explicitly mention 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 is provided on when to use this tool versus siblings like 'fred_release_dates' or 'fred_releases.' There is no mention of prerequisites or when not to use it.

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