Skip to main content
Glama

Market regime for crypto: how BTC and altcoins did in markets like today's

crypto_regime
Read-onlyIdempotent

Is crypto risk-on or risk-off, and what does bitcoin risk look like in markets like today's? Returns the current crypto market regime and each covered coin's typical return and how often it rose over 1, 2 and 3 months when the period started in this regime, as historical odds. $0.01 per call in USDC on Base, Polygon or Solana (x402). Regime updates after each US close, coins once a day. Useful when an agent needs the market regime for crypto across BTC and altcoins. Covers altcoin risk as well as bitcoin.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description is not needed for the safety profile. It still adds genuinely non-obvious context: $0.01 per call paid in USDC on Base, Polygon or Solana via x402 (a cost and payment-rail requirement an agent must plan for), and freshness rules — regime updates after each US close, coins once a day. It stops short of describing response shape or rate/error behavior, which keeps it at 4 rather than 5.

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?

The opening question front-loads the agent's actual decision, followed by return contents, then cost, then freshness — a sensible order for a no-parameter tool. The final two sentences partly restate the title ("Covers altcoin risk as well as bitcoin") and could be cut without losing information.

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?

With no input parameters and no output schema, the description carries full burden for return semantics, and it does explain the core fields and the 1/2/3-month horizons plus update cadence. It never says which regimes exist or which coins are covered, so an agent cannot tell whether its asset of interest is included or what the regime labels actually are.

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 no parameters, which is the baseline-4 case; there is nothing in the schema for the description to elaborate. The description does clarify that output is scoped per covered coin, which is useful framing even though no input exists to disambiguate.

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?

"Returns the current crypto market regime and each covered coin's typical return and how often it rose over 1, 2 and 3 months when the period started in this regime" states a specific resource and a specific computed output, so an agent knows exactly what it gets. It does not name or contrast any sibling (brief, live_reading, stress_gate), so differentiation is implied by topic rather than stated.

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?

"Useful when an agent needs the market regime for crypto across BTC and altcoins" gives a positive use condition, and the opening question frames the risk-on/risk-off question it answers. There is no when-not guidance and no alternative or fallback tool named, so routing between this and the sibling tools is left to inference.

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