Skip to main content
Glama

Get liquidity history

get_liquidity_history
Read-only

Global-liquidity read-history — a timeseries of central-bank liquidity over recent weeks. Returns one row per sample date with the full decomposition (Fed / ECB / BoJ / PBoC in USD trillions), the active basis (g4/g3/us_fallback), the supportive/neutral/draining classification of that week's read, and US net liquidity (us_net_t: Fed balance sheet minus the Treasury General Account minus reverse repo, USD trillions) with its own classification (us_net_class), plus coverage (basis) changes, China-leg publication steps, and classification changes as events. The held money condition, which changes only after two consecutive weekly reads agree, is in get_macro_regime and the Money card of get_dashboard. History companion to get_financial_conditions (Chapter 1 Mode 1.5 Global Liquidity Read). Reading note, enforced by the artifact: when the basis flips g4↔g3 (China PBoC publication freshness), the headline total moves by the ~$7T China component, which is a coverage change rather than a liquidity move. The window trend is therefore computed on constant G3 basis, and every basis flip is listed with an explicit note. A China-leg publication step is a DIFFERENT event and is reported separately: PBoC publishes monthly ~15 days in arrears, so on the day a new statement is recorded the PBoC leg absorbs a whole month of balance-sheet change (plus FX) in one step — real change, but not change that happened on that date, and not the same thing as a coverage flip. The response includes a 'presentation' object whose 'display_markdown' is a pre-formatted table; 'data.rows' and 'summary' carry the same values structured. Rows are provenance-tagged 'observed' (live that day, true vintage) or 'reconstructed' (point-in-time from vintage data — each series as it was published on that date, ~4 months deep). Defaults to the last 12 weeks, weekly. get_indicator_history covers any card or row of get_dashboard over a year, at its own print dates.

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_liquidity_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
intervalNoSample cadence (default weekly)
lookback_weeksNoHow many weeks of history to cover (default 12, clamped 1–52)

Output Schema

NameRequiredDescriptionDefault
dataNo
toolNo
statusNo
summaryNo
warningsNo
generated_atNo
presentationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only/closed-world, so the description adds substantial behavioral context: the g4↔g3 basis-flip coverage caveat (~$7T China component), the separate China-leg publication step (~15 days in arrears), provenance tagging ('observed' vs 'reconstructed', ~4 months deep), and a 'presentation.display_markdown' object. This is well beyond what the structured fields convey.

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?

The core identity is front-loaded in sentence one, and most of the length carries genuine domain caveats an agent needs. However the passage is dense and somewhat repetitive (the coverage-change-vs-liquidity-move point is restated), so it is not maximally tight.

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 a complex, multi-series tool, the definition covers scope, defaults, provenance semantics, event distinctions, and caveats; since an output schema exists, return values need not be spelled out, yet the key shape (rows/summary/presentation) is still noted. Nothing an agent needs to call it correctly is missing.

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% with both parameters documented in-schema, so the baseline is 3. The description only restates the defaults ('last 12 weeks, weekly') already in the schema and adds no format or edge-case detail for interval or lookback_weeks.

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 first sentence states a specific verb+resource+scope: a timeseries of central-bank liquidity over recent weeks, returning one row per sample date with named fields (Fed/ECB/BoJ/PBoC, basis, classification, us_net_t). It explicitly distinguishes itself from siblings, routing the held-money condition to get_macro_regime/get_dashboard and broader coverage to get_indicator_history, and labels itself the history companion to get_financial_conditions.

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?

It gives clear context (history companion to get_financial_conditions; default last 12 weeks weekly) and names the alternative for other data (get_indicator_history covers any card/row over a year). It stops short of an explicit when-not rule, but the routing between this tool and its siblings is easy to infer.

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