Federal Reserve Economic Data (FRED) MCP Server

Browse FRED catalog

fred_browse

Browse and navigate FRED's economic data catalog using categories, releases, or sources to locate specific series.

Instructions

Browse FRED's complete catalog through categories, releases, or sources. Use browse_type='categories' to explore the category tree, 'releases' for data releases, 'sources' for data sources, 'category_series' to get all series in a category, or 'release_series' to get all series in a release.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "browse_type": "<browse_type>"
    },
    "name": "fred_browse"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results
`offset`	No	Number of results to skip
`order_by`	No	Field to order by
`release_id`	No	Release ID (for release_series)
`sort_order`	No	Sort order
`browse_type`	Yes	Type of browsing to perform
`category_id`	No	Category ID (for categories or category_series)
`filter_value`	No	Value to filter the variable by (category_series only)
`filter_variable`	No	Variable to filter by (category_series only)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.0Aug 21, 2026

addedInput schema / properties / filter_value

Added value: +{
+  "description": "Value to filter the variable by (category_series only)",
+  "type": "string"
+}

addedInput schema / properties / filter_variable

Added value: +{
+  "description": "Variable to filter by (category_series only)",
+  "enum": [
+    "frequency",
+    "units",
+    "seasonal_adjustment"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv1.0.1May 2, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedJan 14, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of disclosing behavioral traits. However, it only states that browsing is possible through categories/allows/releases/sources; it does not explicitly state that this is read-only, does not mention pagination behavior, rate limits, return format, or contextual dependencies. Though the word 'browse' implies a read operation, key behavioral expectations remain unstated.

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 two sentences with zero fluff. The first sentence gives a high-level summary, and the second defines each browse_type in a compact list. It is front-loaded and necessary information without redundancy.

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 tool has 9 parameters, no output schema, and no annotations, the description does a solid job of covering the main polymorphic behavior via browse_type. However, it does not address pagination via limit/offset or how filter parameters relate to actual output, though the schema fills some gaps. It is slightly incomplete for full contextual coverage.

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 100%, giving a baseline of 3. The description adds semantic meaning by explaining exactly what each browse_type enum does (e.g., 'category_series' returns all series in a category), which is not fully embedded in the parameter schema's short string description. This goes beyond the schema and meaningfully guides parameter selection.

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 (browse) and resource (FRED's complete catalog), and enumerates the distinct browsing modes: categories, releases, sources, category_series, and release_series. This clearly differentiates it from sibling tools like fred_search and fred_get_series by emphasizing catalog exploration vs searching or retrieving a single 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?

The description provides clear context for using the tool to explore FRED's catalog and details each browse_type variant, but it does not explicitly compare with fred_search or fred_get_series or state when not to use this tool. Since it gives clear operational guidance for internal parameter choices, it meets the 'clear context, no exclusions' bar.

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

Deploy Server