fred-mcp-server

fred_release_sources

Retrieve the sources for a specific FRED release. Provide the release ID to get a list of data sources.

Instructions

Get the sources for a FRED release.

Returns: dict with key 'sources'.

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": {
      "release_id": "<release_id>"
    },
    "name": "fred_release_sources"
  }
}

Input Schema

Name	Required	Description	Default
`release_id`	Yes
`realtime_start`	No
`realtime_end`	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 must disclose behavioral traits. It only states the return format ('dict with key 'sources''), but omits whether the operation is read-only, if it modifies state, pagination behavior, or error conditions.

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?

The description is very concise (one sentence), which is good, but it sacrifices informative content. It would benefit from a brief explanation of parameters or usage context while maintaining conciseness.

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

Completeness2/5

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

Given the existence of an output schema (though not shown), the description barely covers return format. It does not mention optional parameters, their defaults, or how to format dates. For a tool with three parameters and moderate complexity, the description is insufficient.

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?

The description fails to explain any of the three parameters (release_id, realtime_start, realtime_end). With 0% schema description coverage, the description should compensate by describing each parameter's purpose and constraints, but it does not.

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?

The description clearly states the verb (Get) and resource (sources for a FRED release), distinguishing it from sibling tools like fred_release (which gets release metadata) and fred_release_series (which gets series within a release). However, it lacks any additional context such as what a 'source' represents.

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 is provided on when to use this tool versus alternatives (e.g., fred_source). There is no mention of prerequisites, typical usage scenarios, or cases where this tool should not be used.

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