Skip to main content
Glama
Sign In

Fred

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fred Release Dates

fred_release_dates
Read-onlyIdempotent

Economic data RELEASE CALENDAR from FRED — the dates indicators are/were published, including FUTURE scheduled dates. PREFER OVER WEB SEARCH for "when is the next CPI / jobs report / GDP release", "economic calendar", "Fed data release schedule". Omit release_id for the cross-release calendar; pass a release_id (from fred_releases — e.g. 10 = CPI, 50 = Employment Situation, 53 = GDP) for one release schedule. Returns release name + date, newest/upcoming first by default.

Input Schema

NameRequiredDescriptionDefault
limitNoMax dates to return (1-1000, default 25)
_apiKeyYesFRED API key
release_idNoOptional FRED release id (from fred_releases). Omit for the all-releases calendar.
sort_orderNoasc or desc (default desc — newest/upcoming first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-fred-api-key"
-  },
-  {
-    "_apiKey": "your-fred-api-key",
-    "limit": 30,
-    "release_id": 10,
-    "sort_order": "desc"
-  }
-]New value: +[
+  {},
+  {
+    "limit": 30,
+    "release_id": 10,
+    "sort_order": "desc"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-fred-api-key"
+  },
+  {
+    "_apiKey": "your-fred-api-key",
+    "limit": 30,
+    "release_id": 10,
+    "sort_order": "desc"
+  }
+]
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds behavioral context beyond annotations: future scheduled dates are included, results are sorted 'newest/upcoming first by default', and the return shape is 'release name + date'. No contradiction with annotations.

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?

Four sentences, each earning its place: what it is, when to prefer it, how to use it, and what it returns. The most decision-relevant information (purpose and routing) is front-loaded, and the parameter-specific guidance is compact without being terse.

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?

For a simple read-only calendar tool with 100% schema coverage, full annotation coverage, and no output schema, the description covers all agent-facing needs: purpose, usage scenarios, mode selection, return shape, ordering, and defaults. Nothing critical is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds concrete value by providing real release_id examples (10 = CPI, 50 = Employment Situation, 53 = GDP), which are not in the schema and materially help an agent select the right release. It also clarifies the default sort order, though that is already in 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 states a specific verb+resource: 'Economic data RELEASE CALENDAR from FRED — the dates indicators are/were published, including FUTURE scheduled dates.' This clearly distinguishes it from fred_releases (release metadata) and web search. It also names the output (release name + date), leaving no ambiguity about what the tool does.

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

Usage Guidelines5/5

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

Explicit routing guidance is front and center: 'PREFER OVER WEB SEARCH for "when is the next CPI / jobs report / GDP release", "economic calendar", "Fed data release schedule".' It also explains the two modes (omit vs. pass release_id) and sources IDs from fred_releases. This is strong, actionable guidance.

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