Skip to main content
Glama

get_series_updates

Read-onlyIdempotent

Find recently updated FRED economic series, sorted by last-updated time. Filter by macro or regional series or a specific update window.

Instructions

List the FRED series updated most recently (a "what changed" feed, ordered by last-updated time), with pagination metadata. Optionally narrow to macro or regional series, or to a start_time/end_time update window (both required together, YYYY-MM-DDTHH:MM in FRED's timezone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of series to return.
filterNoNarrow to a class of series: `all` (default), `macro`, or `regional`.
end_timeNoEnd of the update time window, same format. Must be given together with `start_time`.
start_timeNoStart of the update time window, `YYYY-MM-DDTHH:MM` in FRED's timezone (to the minute). Must be given together with `end_time`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of matches across all pages.
limitYesPage-size limit that FRED applied.
offsetYesOffset of this page into the full result set.
seriesYesThe matching series on this page. FRED names the array `seriess` (sic) on the wire; we read that but emit the correctly-spelled `series` on output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.7
    • changedOutput schema / $defs / Series / description
      Previous value: -"Metadata describing a FRED series (the `fred/series` endpoint).\n\nALFRED vintage fields (`realtime_start` / `realtime_end`) are deferred for v1\nand ignored on the wire (ADR-0005). `last_updated` is kept as FRED's raw\nstring for now — FRED encodes it with a non-standard timezone offset (e.g.\n`2024-03-28 07:56:03-05`); a typed datetime is a later refinement."New value: +"Metadata describing a FRED series (the `fred/series` endpoint).\n\nThis `series` metadata endpoint's own ALFRED fields (`realtime_start` /\n`realtime_end`) are still ignored on the wire (ADR-0005); point-in-time\n*observations* are supported via [`Observation`](crate::Observation) and\n[`ObservationsRequest::realtime`](crate::ObservationsRequest::realtime)\n(ADR-0024). `last_updated` is kept as FRED's raw string for now — FRED\nencodes it with a non-standard timezone offset (e.g. `2024-03-28 07:56:03-05`);\na typed datetime is a later refinement."
  2. Changed1 schema field changedv0.3.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "Frequency": {
      +      "type": "string"
      +    },
      +    "SeasonalAdjustment": {
      +      "type": "string"
      +    },
      +    "Series": {
      +      "description": "Metadata describing a FRED series (the `fred/series` endpoint).\n\nALFRED vintage fields (`realtime_start` / `realtime_end`) are deferred for v1\nand ignored on the wire (ADR-0005). `last_updated` is kept as FRED's raw\nstring for now — FRED encodes it with a non-standard timezone offset (e.g.\n`2024-03-28 07:56:03-05`); a typed datetime is a later refinement.",
      +      "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"
      +    },
      +    "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": {
      +    "count": {
      +      "description": "Total number of matches across all pages.",
      +      "format": "uint32",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "limit": {
      +      "description": "Page-size limit that FRED applied.",
      +      "format": "uint32",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "offset": {
      +      "description": "Offset of this page into the full result set.",
      +      "format": "uint32",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "series": {
      +      "description": "The matching series on this page. FRED names the array `seriess` (sic) on\nthe wire; we read that but emit the correctly-spelled `series` on output.",
      +      "items": {
      +        "$ref": "#/$defs/Series"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "series",
      +    "count",
      +    "offset",
      +    "limit"
      +  ],
      +  "type": "object"
      +}
  3. First observedv0.3.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds behavioral details beyond annotations: ordering by last-updated time, the mutual requirement of start_time and end_time, and the datetime format hint. 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?

Two sentences with no wasted words. The main purpose is front-loaded, and all additional detail is directly relevant.

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 tool's complexity (4 optional parameters, output schema present), the description fully covers purpose, filtering options, and time window constraints. No gaps.

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 description coverage is 100%, but the description adds value by explaining the filter enum values ('all', 'macro', 'regional') and the mutual requirement of start_time and end_time with format specificity.

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 uses a specific verb 'List' and a clear resource 'FRED series', distinguishes from siblings by focusing on 'updated most recently', and mentions 'pagination metadata' which sets it apart from other series tools.

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 explains when to use ('a 'what changed' feed'), and provides guidance on optional narrowing with filter and time window. It explicitly states that start_time and end_time must be given together, but does not mention alternatives or when not to use.

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