Skip to main content
Glama

Economic series

get_economic_series
Read-onlyIdempotent

A U.S. economic series from FRED: fedfunds (effective fed funds rate), treasury10y, inflation, unemployment, cpi or gdp. Returns the latest value, its date and recent history.

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": "<series>"
    },
    "name": "get_economic_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYesOne of fedfunds, treasury10y, inflation, unemployment, cpi, gdp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds the return shape (latest value, its date, recent history), which is useful context beyond the annotations, but says nothing about units, data source latency, rate limits, or API key needs for FRED.

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?

Two short sentences, front-loaded with the resource and followed by the return contract; nothing is wasted. The series list is restated a second time in the schema, a minor redundancy.

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

Completeness4/5

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

For a single-parameter read-only tool with no output schema, the description is largely sufficient because it states what comes back. The gap is 'recent history' being undefined (how many periods?) and no indication of units (percent vs. index level), which matters for interpreting inflation and cpi.

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?

Schema coverage is 100% and the single parameter is an enum already documented in the schema, so the description only mirrors it. It does gloss 'fedfunds' as the effective fed funds rate, adding a bit of meaning, but leaves the other five series uninterpreted.

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 names a specific resource (a U.S. economic series from FRED) and enumerates exactly which series are available, so an agent knows precisely what it retrieves. It does not differentiate from the sibling get_treasury_yield_curve, which overlaps on the treasury10y concept, leaving a small ambiguity.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives, even though get_treasury_yield_curve is a plausible overlap. Usage is only implied by the phrase 'U.S. economic series'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources