FRED Economic Data

get_category_series

Get all FRED series within a specific category.

FRED organizes data into a hierarchy of categories. Use this to browse
available series within a topic area. Common category IDs:
- 32991: Money, Banking, & Finance
- 10: Population, Employment, & Labor Markets
- 32992: National Accounts (GDP)
- 1: Production & Business Activity
- 32455: Prices (CPI, PPI)
- 97: Housing

Args:
    category_id: FRED category identifier (integer).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A4.4/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 disclose behavioral traits. It describes the action as retrieving all series within a category, which is adequate but lacks details on pagination, limits, or potential side effects. It is acceptable for a read-only tool.

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 and well-structured: a one-line purpose, brief explanation of category hierarchy, common IDs list, and the parameter definition. Every sentence adds value with no redundancy.

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 simplicity (one parameter, no nested objects) and the presence of an output schema, the description provides all necessary context: purpose, usage guidance, and parameter details are sufficient 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds significant value by explaining the parameter as a 'FRED category identifier' and listing common category IDs (e.g., 32991 for Money, Banking, & Finance). This greatly aids correct usage.

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 all FRED series within a specific category' with a specific verb and resource. It distinguishes from siblings like search_series by focusing on browsing by category hierarchy.

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?

It provides context on when to use (browsing series within a topic area) and common category IDs, but does not explicitly mention when not to use or direct alternatives. The context is clear enough for an agent.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?