Skip to main content
Glama

Live market regime: risk-on or risk-off right now

live_reading
Read-onlyIdempotent

Is the US market risk-on or risk-off right now? Returns the live Regime Card reading: a score from 0 (most risk-off) to 100 (most risk-on) and one of five market regimes, from Risk-Off to Risk-On, built from eight cross-asset signals, beside the last settled close. $0.01 per call in USDC on Base, Polygon or Solana (x402). Recomputed hourly during the US session (10:00 AM to 4:00 PM ET) and marked "live". Outside the session it returns the settled reading, marked "settled". Useful when an agent needs a market sentiment or market conditions check for today, or a fear and greed alternative that reads credit, volatility, rates, currencies, commodities and sectors.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish safe read-only, idempotent, open-world behavior, and the description goes well beyond them with operational facts an agent actually needs: $0.01 per call in USDC on Base, Polygon or Solana via x402, hourly recomputation limited to the 10:00 AM-4:00 PM ET US session, and an explicit live-versus-settled marking convention outside that window. Payment requirements and refresh cadence are exactly the kind of pre-call context that prevents failed or wasted invocations. Nothing here conflicts with the annotations.

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 front-loaded with the question and answer shape, then layers cost, cadence, live/settled semantics, and use cases in a logical order with no filler sentences. The one soft spot is the closing clause, which stacks "market sentiment," "market conditions," and "fear and greed alternative" as near-synonyms, adding bulk without adding distinction. Still efficient for the amount of decision-relevant detail it conveys.

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 no output schema and no parameters, the description carries the full burden and meets it: it specifies the score range with endpoint meanings, the five-regime banding, the eight cross-asset inputs (credit, volatility, rates, currencies, commodities, sectors), the accompanying settled close, and the live/settled flag. Cost and recompute timing round out everything an agent needs before committing a paid call. Nothing material is left for the agent to discover the hard way.

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 argument semantics to explain and the schema burden is nil. The description correctly avoids inventing parameter talk and instead spends its words on output shape and timing. Baseline 4 applies for a no-parameter tool; there is simply no additional parameter meaning it could add.

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 description opens with a concrete question the tool answers ("Is the US market risk-on or risk-off right now?") and then states exactly what comes back: a 0-100 score, one of five named regimes, derived from eight cross-asset signals, alongside the last settled close. This is a specific verb+resource statement scoped to the US market, and the title reinforces it. An agent can tell this apart from a generic sentiment tool without reading any 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?

It gives clear when-to-use framing: "useful when an agent needs a market sentiment or market conditions check for today, or a fear and greed alternative." It also implicitly scopes usage by disclosing the $0.01 per-call x402 cost, which lets an agent weigh whether a paid call is warranted. The gap is that no sibling is named as an alternative or exclusion — notably the free sample_reading and the crypto-focused crypto_regime — so the agent must infer the routing decision rather than being told it.

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