TradingAgents MCP

Overview Schema Source Related Servers Discussions Admin

macro_indicator

Fetch macroeconomic data from FRED by indicator alias or raw series ID up to a chosen date, with configurable lookback for trading research.

Instructions

A macro series from FRED up to as_of. Aliases: cpi, core_pce, unemployment, fed_funds_rate, 10y_treasury, yield_curve, real_gdp, vix, ecb_deposit_rate, euro_hicp, eur_usd, or any raw FRED series ID. Needs FRED_API_KEY (free).

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": {
      "indicator": "<indicator>"
    },
    "name": "macro_indicator"
  }
}

Input Schema

Name	Required	Description	Default
`as_of`	No
`indicator`	Yes
`look_back_days`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose two useful facts: the upstream source is FRED and a free FRED_API_KEY is required. It omits series frequency/units, what happens when the key is missing or an alias is unrecognized, and any rate-limit or caching behavior.

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 compact sentences with no filler; the alias enumeration is long but directly serves parameter semantics. The opening sentence is a noun phrase rather than a verb-led statement, a minor structural weakness.

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?

An output schema exists, so return values need no explanation, and the API-key prerequisite is covered. For a 3-parameter tool with zero schema description coverage, the unaddressed look_back_days, the as_of format, and the series frequency are notable omissions.

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 description coverage is 0%, so the description must compensate. It does well for 'indicator' by enumerating accepted aliases plus raw FRED IDs, and it references 'as_of' as an upper bound. But 'look_back_days' (default 365) is never mentioned and the expected format of 'as_of' is unspecified, leaving a meaningful gap.

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 and source ('a macro series from FRED') plus a temporal bound ('up to as_of'), which is enough to distinguish it from equity-oriented siblings like price_history or fundamentals. The verb is implied rather than stated and no sibling is named as an alternative, so it stops short of a 5.

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 long alias list (cpi, core_pce, fed_funds_rate, 10y_treasury, eur_usd, etc.) implicitly tells the agent what kinds of requests belong here, which is genuine usage signal. However, there is no explicit when-to-use versus alternatives statement, no exclusion (e.g. use price_history for equities), and no note on behavior when an alias is unknown.

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