Skip to main content
Glama

Get conditions history

get_conditions_history
Read-only

Financial-conditions read-history — a timeseries of how conditions have moved over recent weeks. Returns one row per sample date with the composite (loose/neutral/tight), direction (easing/stable/tightening), and every pillar's value + class: 10Y real yield, HY/IG credit spreads, DXY, VIX, global-liquidity class. The rate legs behind the real yield are exposed numerically too (dgs10_pct, t10yie_pct, t5yie_pct, t10y2y_pct), so a real-yield move can be read as nominal-led or breakeven-led rather than only as a fused number. Completes the Chapter 1 history trio with get_regime_history (the judgment) and get_liquidity_history (the flow) — this is the price of risk. Surfaces trajectory that a point read hides (e.g. HY spreads widening for six straight weeks while VIX stays calm), and grounds 'conditions are tightening' statements in observed pillar changes. Window deltas per pillar are in 'summary.deltas'; composite/direction/pillar classification changes are listed as events. 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_conditions_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?

Beyond the readOnly/non-destructive annotations, it discloses provenance tagging ('observed' live vintage vs 'reconstructed' point-in-time, ~4 months deep), default window (12 weeks weekly), and response shape (data.rows, summary.deltas, presentation.display_markdown). This is exactly the behavioral context annotations cannot carry.

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?

It is long, but front-loaded with the core identity and each subsequent sentence adds distinct value (pillars, provenance, routing). A few clauses (the full pillar enumeration) border on surplus for a routing decision, keeping it off a 5.

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?

With an output schema present, return-value explanation is optional, yet the description still orients the agent on rows, summary.deltas, events, and the presentation object, while covering scope, defaults, and provenance. Nothing needed to invoke 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% — both interval and lookback_weeks already document cadence and the 1–52 clamp. The description restates the defaults ('last 12 weeks, weekly') without adding syntax or semantics beyond the schema, so baseline 3 applies.

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?

Opening clause 'Financial-conditions read-history — a timeseries of how conditions have moved over recent weeks' gives a specific verb+resource+scope. It explicitly distinguishes itself from siblings get_regime_history (the judgment), get_liquidity_history (the flow), and get_indicator_history (any card over a year). An agent can route without opening a schema.

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?

States the context of use ('grounds tightening statements in observed pillar changes', surfaces trajectory a point read hides) and names the alternative get_indicator_history with its distinct coverage. It does not spell out an explicit when-not condition, so it falls just short of a full routing rubric.

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