ferric-fred-mcp

get_releases_dates

Read-onlyIdempotent

List publication dates of every FRED release, with pagination, sorting, and optional future-date inclusion. Get a complete release calendar.

Instructions

List the publication dates of ALL FRED releases — a release calendar across FRED — with pagination metadata. Each entry names its release. Newest first by default; supports sort direction, a result limit, and including dates that have no data yet.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort direction by date (newest first by default).
`limit`	No	Maximum number of release dates to return.
`include_dates_with_no_data`	No	Include dates that have no data yet, e.g. scheduled future releases (omitted by default).

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Total number of release dates available (across all pages).
`limit`	Yes	The page-size limit that was applied.
`offset`	Yes	The offset (number of dates skipped) for this page.
`release_dates`	Yes	The release dates on this page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.6Jul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ReleaseDate": {
+      "description": "A single scheduled or historical release date, from the\n`fred/releases/dates` and `fred/release/dates` endpoints — the date a\nrelease was (or is scheduled to be) published.",
+      "properties": {
+        "date": {
+          "description": "The date the release was, or is scheduled to be, published.",
+          "format": "date",
+          "type": "string"
+        },
+        "release_id": {
+          "$ref": "#/$defs/ReleaseId",
+          "description": "The release this date belongs to."
+        },
+        "release_name": {
+          "default": null,
+          "description": "The release's name. `releases/dates` (which spans every release)\nincludes it; `release/dates` omits it, since the release is already\nfixed by the request.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "release_id",
+        "release_name",
+        "date"
+      ],
+      "type": "object"
+    },
+    "ReleaseId": {
+      "description": "A FRED release identifier — the numeric id of a data release (a publication\nsuch as \"Gross Domestic Product\").\n\nA `Copy` newtype over `u32`, mirroring [`CategoryId`]; `#[serde(transparent)]`\ncarries it as the bare integer FRED sends (ADR-0005).",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "count": {
+      "description": "Total number of release dates available (across all pages).",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "limit": {
+      "description": "The page-size limit that was applied.",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "offset": {
+      "description": "The offset (number of dates skipped) for this page.",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "release_dates": {
+      "description": "The release dates on this page.",
+      "items": {
+        "$ref": "#/$defs/ReleaseDate"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "offset",
+    "limit",
+    "release_dates"
+  ],
+  "type": "object"
+}

First observedv0.3.2Jul 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds behavioral details: pagination metadata, newest-first default, sort direction, result limit, and inclusion of future dates. No contradictions.

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?

Three sentences, front-loaded with the core purpose. Every sentence adds value without redundancy.

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?

Given the presence of an output schema and comprehensive annotations, the description covers all necessary context: scope, default behavior, and optional parameters.

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 coverage is 100%, so baseline 3. The description restates parameter purposes (sort direction, limit, include dates without data) but does not add new meaning beyond the schema.

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 it lists publication dates of ALL FRED releases, functioning as a release calendar. The use of 'ALL' distinguishes it from sibling tools like 'get_release_dates' which likely filter by a specific release.

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

Usage Guidelines4/5

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

The description implies use for broad calendar view by emphasizing 'ALL FRED releases', indirectly distinguishing from siblings. No explicit when-not or alternative wording, but the context is clear enough.

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