Skip to main content
Glama
mcpwright

fred-mcp

by mcpwright

Compare series

compare_series
Read-only

Align up to five FRED economic time series on a common date axis to compare trends and values. Handles different frequencies when a frequency parameter is provided.

Instructions

Align 2-5 series on one date axis for comparison.

`series_ids`: 2-5 FRED series IDs. Same `start`/`end`/`transform` as
`get_observations`. If the series have DIFFERENT native frequencies you
must pass `frequency` (a frequency at least as coarse as the coarsest
series) — mixing frequencies without it returns misaligned dates. Units
differ per series unless a relative transform (e.g. pct_change_yoy) is
used — check each entry's `units` before comparing levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idsYes
startNo
endNo
transformNolevel
frequencyNo
max_pointsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
seriesYesThe series compared
transformYesThe transform applied to every series
rowsYesAligned values, oldest first
truncatedYesTrue if more rows exist than were returned
Behavior5/5

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

Discloses important behaviors: misalignment if frequency not specified, unit dependency on transform, and the 2-5 series limit, adding value beyond readOnlyHint and openWorldHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, uses efficient bullet-like structure; every sentence adds value, though could be slightly more concise.

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?

Covers core purpose, key caveats, and parameter constraints; defers some parameter details to get_observations, which is acceptable given output schema exists.

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?

Adds meaning for series_ids (2-5 IDs) and frequency (coarse enough), but defers start/end/transform to get_observations and omits max_points, only partially compensating for 0% schema coverage.

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 compares multiple series aligned on one date axis, distinguishing it from single-series tools like get_observations.

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?

Provides clear guidance on when to use the frequency parameter for mixed-frequency series and warns about unit differences, but does not explicitly contrast with sibling tools.

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