Skip to main content
Glama

Market risk brief: regime, stress gate and what happened next

brief
Read-onlyIdempotent

What is the stock market today, in one call? Returns the live market regime reading, the stress gate, and the scorecard row for the current regime: what the S&P 500 did in the 5 and 20 trading days after past readings in this regime (typical return, how often it rose, a bad outcome as a drawdown risk measure). A cross-asset macro signal. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session. Useful when an agent wants one reading as a risk check before a trade or as a position sizing input.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description's real value-add is operational: $0.01 per call in USDC across Base, Polygon or Solana (x402) and hourly recomputation during the US session, which an agent needs to know before calling. It still doesn't describe response shape or how stale a reading can be outside US hours.

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?

Front-loads the core question ('What is the stock market today, in one call?') then enumerates outputs, then cost and refresh cadence. Most sentences earn their place; the 'cross-asset macro signal' fragment is somewhat redundant marketing filler rather than information.

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 no output schema, the description carries the burden of explaining returns, and it does list the components: regime, stress gate, typical return, hit frequency, and a drawdown-based bad-outcome measure. It falls short on how the regime is labelled (categories, units) and what the stress gate actually outputs, which an agent would want before spending a call.

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 the baseline is 4; there is nothing for the description to disambiguate. The statement that the call returns the current regime implicitly confirms the tool is parameter-free (no symbol or date selection needed).

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?

A specific verb ('Returns') plus a concrete set of outputs: live market regime reading, stress gate, and a scorecard row with 5- and 20-day post-regime S&P 500 behavior. It clearly says what the tool delivers, but it never distinguishes itself from siblings like stress_gate or live_reading, which it partly overlaps in content.

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?

Gives two concrete usage contexts: a risk check before a trade, or a position-sizing input. There are no explicit exclusions or named alternatives for when a lighter or more targeted reading (e.g. live_reading, crypto_regime) would be preferable, so guidance is clear but not complete.

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