EL7.AI

Gold macro drivers

el7_gold_macro

Read-onlyIdempotent

Macro series EL7 tracks as gold drivers (FRED): 10Y real yield, breakevens, Fed funds, M2, Fed balance sheet, CPI, Fort Knox reserves, gold-mining output; latest with change, or one series' history, optionally correlation with gold. Use for the rates and inflation backdrop. Dollar and volatility appear only inside el7_gold_overview.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "el7_gold_macro"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Output language: 'en' (default) or 'ar' for EL7's stored Arabic text.
`periods`	No	History length when series_id is given (1-120, default 30).
`series_id`	No	One macro series for its history: DFII10 (10Y real yield), T10YIE / T5YIE (breakeven inflation), DFF (effective Fed funds rate, not the target range), M2SL (M2), WALCL (Fed balance sheet), CPIAUCSL (CPI), FKKYGTA (Fort Knox gold), IPG21222S (gold-mining output index). Omit for the latest value of all.
`include_correlations`	No	Also return the Pearson correlation of each macro series (including dollar and volatility) with gold over about one trading year. Slower; default false.

Output Schema

Name	Required	Description
`url`	Yes
`as_of`	No	Source freshness: the newest source timestamp behind this result, or null when none is verified. Never request time.
`series`	Yes
`correlations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds only a light behavioral note about the correlation mode and the sibling routing; it says nothing about freshness/lag of the FRED series, pagination, or whether 'latest with change' means a single observation per series. Adequate but thin given annotations carry most of the load.

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 tight sentences: the data inventory first, then the usage and sibling boundary, which is good front-loading. Minor waste in re-listing all nine series that the enum already enumerates, but the rest of the sentence earns its place.

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?

With an output schema present, the description need not explain return shapes, and it correctly focuses on which mode is triggered (all-series latest vs single-series history) and on the sibling boundary. It is essentially complete for a read-only retrieval tool; only data-freshness expectations and how 'change' is computed remain unstated.

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 100%, including per-enum meanings for all nine series and the periods range, so the schema does the explanatory work. The description restates the series list rather than adding interpretation beyond it (e.g. why T5YIE vs T10YIE matters, or what a 'change' is measured against). Baseline 3 is appropriate.

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 the concrete resource (FRED macro series tracked as gold drivers) and enumerates exactly what comes back: latest values with change, or a single series' history, plus optional correlation. It also carves out a boundary from el7_gold_overview for dollar and volatility. It stops short of a crisp leading verb, instead leading with a data inventory, which slightly blunts the opening.

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

Usage Guidelines4/5

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

"Use for the rates and inflation backdrop" gives explicit when-to-use guidance, and "Dollar and volatility appear only inside el7_gold_overview" routes the agent to the correct sibling for those inputs. What is missing is a negative case for this tool itself, e.g. when to prefer el7_cb_balance_sheet or el7_calendar_indicator for overlapping Fed/CPI data.

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

All EL7.AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?