Skip to main content
Glama
mcpwright

fred-mcp

by mcpwright

Get series as of a date (vintage)

get_series_as_of
Read-only

Retrieve a FRED economic time series exactly as it was known on a specified past date, before any later revisions.

Instructions

A series EXACTLY as it was known on a past date — before later revisions.

`series_id`: a FRED series ID. `as_of`: the knowledge date (ISO) — e.g.
"2009-03-18" shows the data the Fed saw at its March 2009 meeting.
`start`/`end` bound the observation window as usual.

Vintage coverage varies by series: dates before the first vintage have no
data (check `get_vintage_dates`). Values can differ sharply from today's —
that's the point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idYes
as_ofYes
startNo
endNo
max_pointsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idYesThe FRED series ID
titleYesSeries title (current title)
as_ofYesThe knowledge date — values are as published on this date, before any later revisions
unitsYesUnits of the values
observationsYesThe data as known on as_of, oldest first
truncatedYesTrue if more observations exist than were returned
Behavior4/5

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

Annotations indicate readOnlyHint and openWorldHint. The description adds beyond that by mentioning that vintage coverage varies, dates before the first vintage have no data, and values can differ sharply from today's. This informs the agent about expected behavior and limitations, complementing the annotations without 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?

The description is concise (approx. 80 words) and well-structured: a clear purpose statement, followed by parameter explanations and behavioral notes. Every sentence adds value with no redundancy or fluff, achieving optimal density of information.

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 complexity of vintage data retrieval and the presence of an output schema, the description covers the core concept, parameter usage, and key behavioral nuance (vintage coverage). It references a sibling tool for further checking. It does not discuss the output format or pagination, but the output schema likely handles that. Overall, it is adequately complete for an agent to use the tool correctly.

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 0%, so the description must compensate. It explains 'series_id' and 'as_of' well, including an example, and describes 'start' and 'end' as bounding the observation window. However, 'max_points' is not mentioned at all. With 5 parameters and only partial coverage, the description adds some meaning but leaves a gap.

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's purpose: retrieving a series exactly as it was known on a past date, before later revisions. It distinguishes itself from siblings like 'get_observations' (current data) and 'get_revision_history' (tracking changes) by emphasizing the vintage aspect, providing a specific verb-resource-scope.

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 concrete usage context, such as showing data the Fed saw at a meeting, and advises to check 'get_vintage_dates' for coverage. It implies when to use (for historical revisions) and when not to (for current data), though it does not explicitly list alternatives. The guidance is clear and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcpwright/fred-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server