ferric-fred-mcp

get_series

Read-onlyIdempotent

Fetch metadata for a FRED series by ID: title, frequency, seasonal adjustment, units, observation date range, and popularity.

Instructions

Fetch metadata for a FRED series by its id (e.g. GNPCA, UNRATE): title, frequency, seasonal adjustment, units, observation date range, and popularity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`series_id`	Yes	The FRED series id, e.g. `GNPCA` or `UNRATE`.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The series identifier.
`notes`	Yes	Editorial notes, when present.
`title`	Yes	Human-readable title, e.g. `"Real Gross National Product"`.
`units`	Yes	Free-form units description, e.g. `"Billions of Chained 2017 Dollars"`. This is descriptive text, not the closed-vocabulary units transform used in observation requests (modelled separately, later).
`frequency`	Yes	The series' native reporting frequency.
`popularity`	Yes	FRED popularity score (0–100).
`last_updated`	Yes	When FRED last updated the series, as FRED's raw timestamp string.
`observation_end`	Yes	Date of the latest available observation.
`observation_start`	Yes	Date of the earliest available observation.
`seasonal_adjustment`	Yes	Whether/how the series is seasonally adjusted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.6Jul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Frequency": {
+      "type": "string"
+    },
+    "SeasonalAdjustment": {
+      "type": "string"
+    },
+    "SeriesId": {
+      "description": "A FRED series identifier, e.g. `GNPCA` or `UNRATE`.\n\nA newtype over `String` so a series id can't be silently swapped for another\nkind of identifier or an arbitrary string (see ADR-0005). Construction does\nno validation for now — FRED rejects malformed ids — but the newtype gives\nus a place to add it later without changing call sites.",
+      "type": "string"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "frequency": {
+      "$ref": "#/$defs/Frequency",
+      "description": "The series' native reporting frequency."
+    },
+    "id": {
+      "$ref": "#/$defs/SeriesId",
+      "description": "The series identifier."
+    },
+    "last_updated": {
+      "description": "When FRED last updated the series, as FRED's raw timestamp string.",
+      "type": "string"
+    },
+    "notes": {
+      "default": null,
+      "description": "Editorial notes, when present.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "observation_end": {
+      "description": "Date of the latest available observation.",
+      "format": "date",
+      "type": "string"
+    },
+    "observation_start": {
+      "description": "Date of the earliest available observation.",
+      "format": "date",
+      "type": "string"
+    },
+    "popularity": {
+      "description": "FRED popularity score (0–100).",
+      "format": "uint32",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "seasonal_adjustment": {
+      "$ref": "#/$defs/SeasonalAdjustment",
+      "description": "Whether/how the series is seasonally adjusted."
+    },
+    "title": {
+      "description": "Human-readable title, e.g. `\"Real Gross National Product\"`.",
+      "type": "string"
+    },
+    "units": {
+      "description": "Free-form units description, e.g. `\"Billions of Chained 2017 Dollars\"`.\nThis is descriptive text, *not* the closed-vocabulary units transform\nused in observation requests (modelled separately, later).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "observation_start",
+    "observation_end",
+    "frequency",
+    "seasonal_adjustment",
+    "units",
+    "popularity",
+    "notes",
+    "last_updated"
+  ],
+  "type": "object"
+}

First observedv0.3.2Jul 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds specific metadata fields returned, which is helpful behavioral context beyond the 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?

Single sentence, well-front-loaded with the verb 'Fetch metadata' and includes key details. No unnecessary words.

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 simple single-parameter tool and the presence of an output schema, the description adequately lists the returned metadata fields, making it complete for agent use.

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 provides an example of series_id but does not add meaning beyond what the schema already states. Baseline 3 is appropriate.

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 tool fetches metadata for a FRED series by its id, listing specific metadata fields (title, frequency, etc.), distinguishing it from sibling tools that deal with categories, releases, or tags.

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 for retrieving series metadata but does not explicitly state when to use vs. alternatives or when not to use it. Sibling tools are listed but no comparison is made.

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