FRED Economic Data

get_series_info

Get metadata and details for a specific FRED series.

Returns comprehensive information about a series including its title,
frequency, units, seasonal adjustment, source, and date range. Use this
to understand what a series measures before pulling observations.

Args:
    series_id: FRED series identifier (e.g. 'UNRATE', 'GDP', 'CPIAUCSL').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`series_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It describes the return information but does not explicitly state it is read-only, safe, or mention any prerequisites like API keys. Assumes safe read operation but lacks explicit disclosure.

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?

Extremely concise: two sentences plus an Args block. Front-loaded with main purpose. Every sentence adds value with no fluff.

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 only one parameter, no nested objects, and an existing output schema, the description is fairly complete. It covers what the tool returns and when to use it, though it could mention that it is a safe read operation.

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 0%, but the description provides meaningful guidance for the sole parameter series_id: 'FRED series identifier (e.g. 'UNRATE', 'GDP', 'CPIAUCSL')'. This adds valuable context beyond the raw 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 clearly states 'Get metadata and details for a specific FRED series' and lists specific return fields (title, frequency, units, etc.). It distinguishes from siblings like get_series_observations (data points) and search_series.

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?

Explicitly advises 'Use this to understand what a series measures before pulling observations,' providing clear context for appropriate use. Does not explicitly exclude scenarios or name alternatives.

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

All FRED Economic Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: get_category_series browses series by category, get_release_dates tracks publication dates, get_series_info provides metadata, get_series_observations retrieves data points, and search_series finds series by keyword. The descriptions reinforce these unique roles, eliminating any ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes and descriptive nouns (e.g., get_category_series, search_series). The naming is uniform and predictable, making it easy for agents to understand the action and target resource.

Tool Count5/5

With 5 tools, this server is well-scoped for accessing FRED economic data. It covers essential operations like searching, retrieving metadata, and fetching observations, without being overly sparse or bloated. Each tool serves a clear purpose in the data exploration workflow.

Completeness4/5

The tool set provides strong coverage for browsing and retrieving economic data, including search, metadata, and observations. However, it lacks direct update or manipulation tools (e.g., for user favorites or annotations), which are minor gaps but not critical for the core domain of data access.

Resources

Need Help?