fred-mcp-server

fred_sources

Retrieve all sources of economic data from the FRED API, with optional filtering, pagination, and sorting.

Instructions

Get all sources of economic data.

Returns: dict with key 'sources'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fred_sources"
  }
}

Input Schema

Name	Required	Description	Default
`realtime_start`	No
`realtime_end`	No
`limit`	No
`offset`	No
`order_by`	No
`sort_order`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2May 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden. Only states return format (dict with 'sources'), but lacks details on pagination, rate limits, data freshness, or other behavioral traits.

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

Conciseness3/5

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

Very concise but too terse; missing crucial information. Could include parameter hints or output schema details while remaining short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, no annotations, output schema exists but not described, and many sibling tools, the description is highly incomplete. Fails to explain pagination, sorting, or differences from similar tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

Schema coverage is 0% and description mentions no parameters. All 6 optional parameters are undocumented, providing no meaning beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Get all sources of economic data', which is a clear verb+resource. Differentiates from 'fred_source' (singular) by implication of plural, but does not explicitly compare to siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like 'fred_source' or 'fred_releases'. Does not mention context such as filtering or typical use cases.

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