Skip to main content
Glama

Get financial conditions

get_financial_conditions
Read-only

Full financial conditions read, the detail behind the Money and Financial conditions cards of get_dashboard (and the regime's Money row): global liquidity (Fed + ECB + BoJ central-bank balance sheets, FX-converted to USD; PBoC included when a fresh Mako-curated publication is available — basis 'g4' vs 'g3'), the 10-year real yield with its nominal and breakeven legs, HY/IG credit spreads, the dollar index (DXY), VIX. Inside global liquidity: us_net_liquidity (Fed balance sheet minus the Treasury General Account minus overnight reverse repo, with 4- and 12-week changes, its own classification and dated inputs; a supporting read, not part of the regime light) and change_decomposition (for the 4- and 12-week windows, how much of the change in dollars came from the balance sheets themselves and how much from exchange rates, which dominated, and the method). Returns composite + direction + per-pillar classifications + drivers. The scope and scope_note fields tell you whether the read is G4 or G3, and the China sub-component carries Mako-curated provenance (as_of_month, source_url, note). Pass summary_only:true for the lightweight one-line read used in regime composition.

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

Input Schema

NameRequiredDescriptionDefault
summary_onlyNoIf true, return composite + direction + one-line driver only

Output Schema

NameRequiredDescriptionDefault
as_ofNo
scopeNo
driversNo
pillarsNo
compositeNo
directionNo
scope_noteNo
data_sourcesNo
terms_glossaryNo
staleness_flagsNo

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

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive, so the description correctly spends its words elsewhere: it discloses that PBoC inclusion depends on a fresh Mako-curated publication (basis 'g4' vs 'g3'), that us_net_liquidity is 'a supporting read, not part of the regime light', and that scope/scope_note carry provenance. This is substantive behavioral context an agent could not get from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is effectively one enormous sentence stitched together with em-dashes and nested parentheses, and much of it (the us_net_liquidity formula, change_decomposition method) describes return-value internals that the existing output schema already covers. It is front-loaded on purpose but far heavier than a single-parameter read tool needs.

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 is not obligated to explain return values, yet it goes further and clarifies scope semantics, China provenance, and the summary_only shortcut. Coverage is strong; the only miss is not positioning the tool against overlapping siblings like get_liquidity_history.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents summary_only's boolean meaning. The description adds only that the lightweight read is 'used in regime composition', which is marginal value over the schema text; baseline 3 is appropriate.

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 opening clause names a specific verb and resource ('Full financial conditions read') and immediately anchors it to concrete outputs (the Money/Financial conditions cards of get_dashboard and the regime's Money row). It enumerates the exact pillars returned (global liquidity, real yield, credit spreads, DXY, VIX), which makes it unmistakable against siblings like get_china_liquidity, get_liquidity_history, or get_macro_regime.

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 only genuine usage steering is 'Pass summary_only:true for the lightweight one-line read used in regime composition', which tells the agent when to use the flag variant but not when to prefer this tool over siblings such as get_liquidity_history or get_china_liquidity. There is no explicit when-not guidance, so usage is implied rather than stated.

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