ferric-fred-mcp

get_releases

Read-onlyIdempotent

List FRED releases (publications like GDP) with pagination, sorting, and limit options.

Instructions

List FRED data releases (publications such as "Gross Domestic Product"), with pagination metadata. A browse axis parallel to categories. Supports sort direction and a result limit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Sort direction by release id.
`limit`	No	Maximum number of releases to return.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Total number of releases available (across all pages).
`limit`	Yes	The page-size limit that was applied.
`offset`	Yes	The offset (number of releases skipped) for this page.
`releases`	Yes	The releases 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": {
+    "Release": {
+      "description": "A FRED data release — a publication such as \"Gross Domestic Product\", from\nthe `fred/release` and `fred/releases` endpoints.",
+      "properties": {
+        "id": {
+          "$ref": "#/$defs/ReleaseId",
+          "description": "The release's identifier."
+        },
+        "link": {
+          "default": null,
+          "description": "A link to the release on the source's site, when FRED provides one.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Human-readable name, e.g. `\"Gross Domestic Product\"`.",
+          "type": "string"
+        },
+        "press_release": {
+          "description": "Whether the release is accompanied by a press release.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "press_release",
+        "link"
+      ],
+      "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 releases 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 releases skipped) for this page.",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "releases": {
+      "description": "The releases on this page.",
+      "items": {
+        "$ref": "#/$defs/Release"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "offset",
+    "limit",
+    "releases"
+  ],
+  "type": "object"
+}

First observedv0.3.2Jul 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds behavioral context by mentioning 'pagination metadata' and describing the tool as a browse axis, which is beyond what annotations provide. No contradiction.

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 concise sentences, front-loaded with the primary action. Each sentence adds value: purpose, analogy, capabilities. No unnecessary words.

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?

Given the tool's simplicity (2 optional parameters, rich annotations, output schema present), the description covers the essential purpose and key features. It doesn't explain return values, but the output schema handles that. Minor gap: could clarify pagination metadata structure, but overall sufficient.

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%, so the schema already documents both parameters (sort and limit) with descriptions. The description adds little beyond stating 'Supports sort direction and a result limit', which doesn't provide additional semantic detail over 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 the verb 'List' and resource 'FRED data releases', providing an example 'Gross Domestic Product'. It differentiates from sibling tools by describing it as a browse axis parallel to categories, thus distinguishing it from other release-related tools like get_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 provides context for when to use this tool ('A browse axis parallel to categories'), implying it's for browsing releases similarly to category browsing. However, it lacks explicit exclusions or guidance on when to use alternatives like get_release or get_release_dates.

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