Skip to main content
Glama

Market stress gate: credit, volatility, rates

stress_gate
Read-onlyIdempotent

Is there market stress right now in credit, volatility or rates? Returns the Regime Card stress gate in one call: Calm, Elevated or Stressed, how many of its three components are confirmed (N of 3), and each component (Credit, Volatility, Rates) as Clear or Confirmed. States only, never the levels behind them. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session. "stale" is true when a scheduled update is missing. Useful when an agent needs a market stress or market risk check on credit, volatility and rates before it acts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses the exact output shape (state, N of 3, per-component Clear/Confirmed), the key limitation that only states are returned and never levels, the $0.01 USDC payment across three chains, hourly recomputation during the US session, and the meaning of the stale flag. These are material behavioral details an agent needs before paying for and relying on the result.

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

Conciseness5/5

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

The description is front-loaded with the core question and return shape, then covers constraints, pricing, freshness and the stale edge case in tightly packed sentences. Every sentence adds necessary information for a paid, no-parameter data tool.

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?

Given zero parameters, no output schema and rich annotations, the description supplies the missing return semantics, payment model, freshness cadence and stale behavior. An agent has enough information to decide whether to call it and how to interpret the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain. The baseline for zero parameters is 4, and the description does not need to compensate for any schema gap.

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 states a specific resource and output: the Regime Card stress gate covering credit, volatility and rates, returning Calm/Elevated/Stressed plus component confirmations. It does not explicitly distinguish this from similarly named siblings such as crypto_regime or live_reading, so it is clear but lacks sibling differentiation.

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 a clear usage context: 'Useful when an agent needs a market stress or market risk check on credit, volatility and rates before it acts.' It does not name when not to use it or point to specific alternatives, but the when-to-use condition is explicit.

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