Retrieve all releases associated with a specified FRED data source. Use a source ID to get release details like IDs, names, and dates.
Get the releases for a source.
Returns: dict with key 'releases'.
| Name | Required | Description | Default |
|---|---|---|---|
| source_id | Yes | ||
| realtime_start | No | ||
| realtime_end | No | ||
| limit | No | ||
| offset | No | ||
| order_by | No | ||
| sort_order | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description only mentions the return type ('dict with key 'releases''), lacking details on required permissions, error handling, 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (2 sentences) and front-loaded with the purpose, containing no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having 7 parameters and no schema descriptions, the description fails to explain pagination (limit, offset), ordering, realtime dates, or any other context, making it highly incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain any of the 7 parameters, providing no additional meaning beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's action ('Get') and resource ('releases for a source'), distinguishing it from siblings like fred_releases (all releases) and fred_source (source info).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, no exclusions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/floriancaro/fred-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server