fred-mcp-server

fred_release_dates

Retrieve release dates for a specified FRED release ID. Filter by real-time period, limit, and sort order.

Instructions

Get release dates for a specific FRED release.

Args: release_id: FRED release ID. 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. 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

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": {
      "release_id": "<release_id>"
    },
    "name": "fred_release_dates"
  }
}

Input Schema

Name	Required	Description	Default
`release_id`	Yes
`realtime_start`	No
`realtime_end`	No
`limit`	No
`offset`	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

A4/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits beyond basic functionality. It omits potential side effects, permissions, rate limits, or whether dates include future events.

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?

The description is concise, front-loaded with purpose, followed by a clear parameter list and return type. Every sentence adds value.

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 7 parameters and no annotations or output schema, the description adequately covers purpose, all parameters, and return format ('dict with key release_dates'), making it complete for tool invocation.

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

Parameters5/5

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

The description explains each of the 7 parameters in the Args section, adding meaning beyond the schema which has no descriptions and only 0% coverage. This enables correct parameter usage.

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 'Get release dates for a specific FRED release', using a specific verb and resource, and distinguishes from siblings like fred_release or fred_releases_dates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a release_id and need its dates, but provides no explicit guidance on when to use this tool versus alternatives like fred_releases_dates or fred_release.

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