Skip to main content
Glama
floriancaro

fred-mcp-server

by floriancaro

fred_series_release

Retrieve release information for a specific FRED series. Provide the series_id and optional realtime dates to get the associated release data.

Instructions

Get the release for a FRED series.

Returns: dict with key 'releases'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idYes
realtime_startNo
realtime_endNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states return structure but no side effects, auth requirements, or rate limits.

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

Conciseness4/5

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

Extremely concise with two short sentences. No wasted words, but could benefit from slightly more detail without sacrificing 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 3 parameters, no annotations, and many sibling tools, the description is incomplete. It fails to explain parameters or provide usage context.

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 description coverage is 0%, and description provides no explanation of parameters. 'series_id', 'realtime_start', and 'realtime_end' are not described, leaving their meaning unclear.

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 clearly states 'Get the release for a FRED series' with verb and resource. However, it does not differentiate from siblings like 'fred_release' or 'fred_release_series', which have similar purposes.

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 versus alternatives such as 'fred_release' or 'fred_release_series'. The description lacks context for selecting the right tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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