Skip to main content
Glama

market_stress_v1

🔒 PREMIUM (not available anonymously on this endpoint): [EVIDENCE v1.1] US financial stress composite (VIX, HY spread, TED spread, STLFSI) as evidence only. Returns reason_codes + signal_strength + risk_band. Rebuilt from retired macroracle — NO stress_level categorical (LOW/MODERATE/HIGH/EXTREME).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses an auth constraint (premium, unavailable anonymously) and negative specification (no LOW/MODERATE/HIGH/EXTREME categorical), which prevents an agent from parsing a field that no longer exists. It still omits rate limits, caching, and the semantics of signal_strength's scale.

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?

Three dense sentences with the access constraint and the return contract front-loaded. There is mild redundancy in saying 'evidence' twice ('[EVIDENCE v1.1]' plus 'as evidence only') and a version tag that adds little for the caller.

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

Completeness3/5

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

For a parameterless tool with no output schema, the description must explain the return payload, and it lists reason_codes, signal_strength and risk_band. However, it never defines those fields, and it is unclear how risk_band differs from the explicitly removed stress_level categorical, leaving a real gap at the call site.

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 nothing for the description to disambiguate beyond what the empty schema already states. The baseline of 4 applies.

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 names a concrete resource and its constituents: a US financial stress composite built from VIX, HY spread, TED spread and STLFSI. It also distinguishes itself from its predecessor ('rebuilt from retired macroracle') and from the categorical form ('NO stress_level'). It stops short of differentiating it from live siblings like recession_risk_v1 or macro_coherence_v1.

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?

'as evidence only' implies a supporting/inputs role rather than a decision-grade indicator, and the premium gate tells the agent when the call will fail. There is no explicit statement of when to prefer this over recession_risk_v1 or macro_coherence_v1, which cover adjacent risk territory.

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.