fred-mcp-server

geofred_series_group

Retrieve metadata for a geographic FRED series, including title, region type, series group ID, seasonality, units, frequency, and date range. Provide a series ID to get details.

Instructions

Get metadata for a geographic FRED series.

Returns metadata including title, region type, series group ID, seasonality, units, frequency, and date range.

Returns: dict with key 'series_group'.

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": {
      "series_id": "<series_id>"
    },
    "name": "geofred_series_group"
  }
}

Input Schema

Name	Required	Description	Default
`series_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2May 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It states it returns metadata but doesn't disclose if it's read-only, any authentication needs, or side effects. Minimal beyond purpose.

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?

Short and to the point, with main purpose front-loaded. No wasted words, though it could be more structured with parameter description.

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

Completeness3/5

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

Adequately covers a simple metadata retrieval tool with one parameter. The output schema exists but description only gives a hint. With many siblings, more detail on when to use would improve completeness.

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 single parameter series_id has zero description coverage in schema and no explanation in description. Agent is left to infer what series_id represents.

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?

Clearly states it retrieves metadata for a geographic FRED series, listing included fields. It differentiates from siblings like fred_series (non-geographic) and geofred_series_data (data values). Could be more explicit about the distinction.

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?

Provides no guidance on when to use this tool versus the many sibling tools. No when-not-to-use or alternative suggestions.

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