Skip to main content
Glama

Fred

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fred Releases

fred_releases
Read-onlyIdempotent

Check upcoming and recent economic data releases. Returns release dates, names, and which series they update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-1000, default 20)
offsetNoResult offset for pagination (default 0)
_apiKeyYesFRED API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPresent when the release list was truncated.
releasesYesList of economic data releases
returnedNoHow many releases are in `releases` (capped by `limit`, default 20).
truncatedNoTrue when `returned` is less than `total_releases`.
total_releasesYesTotal number of releases

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-fred-api-key",
-    "limit": 20
-  }
-]New value: +[
+  {
+    "limit": 20
+  }
+]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "Present when the release list was truncated.",
+  "type": "string"
+}
    • addedOutput schema / properties / returned
      Added value: +{
+  "description": "How many releases are in `releases` (capped by `limit`, default 20).",
+  "type": "number"
+}
    • addedOutput schema / properties / truncated
      Added value: +{
+  "description": "True when `returned` is less than `total_releases`.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "releases": {
+      "description": "List of economic data releases",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Release ID",
+            "type": "number"
+          },
+          "link": {
+            "description": "URL link to release details",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Name of the release",
+            "type": "string"
+          },
+          "notes": {
+            "description": "Additional notes about the release",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "press_release": {
+            "description": "Whether this is a press release",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "press_release",
+          "link",
+          "notes"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_releases": {
+      "description": "Total number of releases",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_releases",
+    "releases"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-fred-api-key",
+    "limit": 20
+  }
+]
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety traits. It adds behavioral value by disclosing the output scope (release dates, names, associated series), which is not present in annotations or schema. No contradiction with annotations is present.

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?

Two short sentences, front-loaded with the action and scope ('Check upcoming and recent economic data releases'), followed by a precise list of return fields. No filler, no redundancy, and every sentence serves a purpose.

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 that an output schema exists and annotations carry the read-only/idempotent safety profile, the description supplies the main missing semantic context: what a 'release' is and what kind of data comes back. It does not cover when to prefer this over fred_release_dates, which is a minor gap given the information available elsewhere.

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% and the description adds no parameter-specific meaning beyond what the input schema already documents for limit, offset, and _apiKey. It does not explain how pagination or the API key relate to behavior, so it stays at the baseline rather than adding value.

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 states the resource is 'upcoming and recent economic data releases' and the action is 'check', and it specifies the return content: 'release dates, names, and which series they update.' This gives a clear sense of the tool's function, though it does not explicitly differentiate from the sibling fred_release_dates, which could be confused for a date-focused variant.

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 temporal qualifier 'upcoming and recent' implies when the tool is relevant, but there is no explicit guidance about when to use this tool instead of alternatives like fred_release_dates, fred_search, or fred_get_series. No alternatives are named and no exclusions are provided, leaving usage mostly inferable rather than directed.

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

All Fred toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources