Skip to main content
Glama

Get macro / market history

get_macro_history
Read-only

Historical time series behind the Global Markets dashboard, often decades long: equity indices, central-bank policy rates, 10-year government bond yields, FX rates, oil/gas/gold/copper, VIX, the broad dollar index, the US 2s10s curve, and per-country macro indicators (GDP growth, inflation, unemployment, house prices, credit gap, debt, confidence, macro stress). Address a series by historyCode (from get_global_markets_overview, get_country_macro or get_macro_indicators), by instrument name ("Fed", "Brent", "Germany 10Y", "S&P 500"), or by indicator + country. Returns summary statistics (latest, change over 1M/3M/1Y/5Y, range, where the latest sits in the window) plus resampled points. Use for "how have rates moved since 2022", "plot Brent over 10 years", "is German unemployment rising". Read-only.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (inclusive).
codeNoExact series code from another tool's historyCode field (e.g. "BIS_CBPOL_US", "UNEMPLOYMENT:Germany").
fromNoStart date YYYY-MM-DD (inclusive).
countryNoCountry for indicator, e.g. "Japan".
intervalNoResample to end-of-period values. auto = the finest interval that fits maxPoints.auto
indicatorNoOr a per-country macro indicator, together with country (same keys as get_macro_indicators).
maxPointsNoUpper bound on returned points (auto interval only; an explicit interval is truncated to the most recent maxPoints).
instrumentNoOr a market name: an index ("S&P 500", "DAX", "Nikkei 225"), commodity ("Brent", "Gold"), FX pair ("EUR/USD"), central bank ("Fed", "ECB", "BoE"), 10Y yield ("Germany 10Y", "US 10Y"), or headline series ("VIX", "dollar index", "2s10s", "global inflation").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / instrument / description
      Previous value: -"Or a market name: an index (\"S&P 500\", \"DAX\", \"Nikkei 225\"), commodity (\"Brent\", \"Gold\"), FX pair (\"EUR/USD\"), central bank (\"Fed\", \"ECB\", \"BoE\"), 10Y yield (\"Germany 10Y\", \"US 10Y\"), or headline series (\"VIX\", \"DXY\", \"2s10s\", \"global inflation\")."New value: +"Or a market name: an index (\"S&P 500\", \"DAX\", \"Nikkei 225\"), commodity (\"Brent\", \"Gold\"), FX pair (\"EUR/USD\"), central bank (\"Fed\", \"ECB\", \"BoE\"), 10Y yield (\"Germany 10Y\", \"US 10Y\"), or headline series (\"VIX\", \"dollar index\", \"2s10s\", \"global inflation\")."
  2. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"Exact series code from another tool's historyCode field (e.g. \"CNBC_US10Y\", \"BIS_CBPOL_US\", \"UNEMPLOYMENT:Germany\", \"YAHOO_GSPC\")."New value: +"Exact series code from another tool's historyCode field (e.g. \"BIS_CBPOL_US\", \"UNEMPLOYMENT:Germany\")."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description reinforces "Read-only." It adds real behavioral context beyond that: series can be decades long, the response carries summary statistics over multiple windows plus resampled points, and points may be truncated. Pagination/token-size behavior is only implied via maxPoints.

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?

Front-loaded with what data exists, then addressing modes, then return shape, then read-only status. The long enumeration of commodities and indicators is dense but serves discovery of what is queryable; minor trimming is possible.

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

Completeness5/5

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

For an 8-parameter, all-optional tool with no output schema, the description covers what series exist, how to address them, what comes back, and the safety profile. An agent has enough to call this correctly without further inference.

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%, so the schema already documents each parameter including examples. The description adds the useful cross-parameter insight that code, instrument, and indicator+country are alternative addressing modes, but it does not explain precedence if more than one is supplied. Baseline 3 applies where the schema does the heavy lifting.

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?

States a specific verb and resource (historical time series for the Global Markets dashboard) and enumerates the concrete series families it covers plus addressable inputs. It distinguishes itself from get_global_markets_overview, get_country_macro and get_macro_indicators by positioning those as code sources rather than substitutes.

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?

Gives three concrete usage examples ("how have rates moved since 2022", "plot Brent over 10 years", "is German unemployment rising") and explains the three ways to address a series. It does not state explicit exclusions or when to prefer a sibling instead, so it stops short of full when/when-not guidance.

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.