Skip to main content
Glama
Sign In
fred-economic-intelligence-mcp

fred-economic-intelligence-mcp

by prithvi1029
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_series_metadata

Retrieve metadata for a FRED economic series by providing its series ID, such as GDP or UNRATE. Get details like title, units, and frequency.

Instructions

Retrieve metadata for a FRED economic series.

Examples of series IDs:
GDP, CPIAUCSL, UNRATE, FEDFUNDS.

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": "get_series_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description bears full burden. It only says 'metadata' without specifying what fields are returned (e.g., title, frequency, units) or any side effects, authentication needs, 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.

Conciseness5/5

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

One concise sentence plus a list of examples. No superfluous words; every element serves a purpose.

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?

Though the tool is simple and an output schema exists, the description does not clarify what 'metadata' includes. For an agent, more context on the returned structure would be helpful.

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

Parameters3/5

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

Only one parameter 'series_id' with 0% schema description coverage, so description must compensate. The examples of series IDs add semantic context but lack format constraints or allowed values, so baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states 'Retrieve metadata for a FRED economic series' with specific verb and resource. Examples of series IDs like GDP and UNRATE help distinguish from sibling tools such as get_series_observations or search_series.

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

Usage Guidelines3/5

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

The description implies usage for retrieving metadata but provides no explicit when-to-use or when-not-to-use guidance, nor references to alternative tools among the siblings.

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

Deploy Server

Other Tools