AlgoVault — Crypto Quant Trade Calls

get_market_regime

Read-only

Returns the market regime — TRENDING_UP TRENDING_DOWN RANGING VOLATILE — with confidence and a strategy hint, for one crypto perpetual futures. Composite verdict: trend ranging + cross-venue funding rate. Read-only, live exchange APIs. Verified track record: get_track_record or performance://signal-performance; on-chain verified merkle anchor.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	Yes	Base asset crypto signal, e.g. BTC ETH SOL signal. Crypto quant regime.
`exchange`	No	Crypto venue, e.g. Binance Bybit OKX Bitget Hyperliquid. Multi-exchange.	HL
`timeframe`	No	Candle timeframe, e.g. 1h 4h 1d. Buy sell hold AI trading signal context.	4h

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 4, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "BINGX",
-  "GATE",
-  "HTX",
-  "KUCOIN",
-  "MEXC",
-  "PHEMEX",
-  "WHITEBIT",
-  "XT"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "BINGX",
+  "GATE",
+  "HTX",
+  "KUCOIN",
+  "MEXC",
+  "PHEMEX",
+  "WHITEBIT",
+  "XT",
+  "WEEX"
+]

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "BINGX",
-  "GATE",
-  "HTX",
-  "KUCOIN",
-  "MEXC",
-  "PHEMEX",
-  "WHITEBIT",
-  "BITMART",
-  "XT"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "BINGX",
+  "GATE",
+  "HTX",
+  "KUCOIN",
+  "MEXC",
+  "PHEMEX",
+  "WHITEBIT",
+  "XT"
+]

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE",
-  "MEXC",
-  "KUCOIN",
-  "PHEMEX",
-  "BINGX",
-  "HTX",
-  "WEEX",
-  "BITMART",
-  "XT",
-  "WHITEBIT"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "BINGX",
+  "GATE",
+  "HTX",
+  "KUCOIN",
+  "MEXC",
+  "PHEMEX",
+  "WHITEBIT",
+  "BITMART",
+  "XT"
+]

Changed3 schema fields changedJun 17, 2026

changedInput schema / properties / coin / description

Previous value: -"Asset symbol — BTC ETH SOL signal. Crypto quant trade call classification."New value: +"Base asset crypto signal, e.g. BTC ETH SOL signal. Crypto quant regime."

changedInput schema / properties / exchange / description

Previous value: -"Exchange BINANCE HL BYBIT OKX BITGET. Multi-exchange Claude trading agent."New value: +"Crypto venue, e.g. Binance Bybit OKX Bitget Hyperliquid. Multi-exchange."

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe — 1h 4h 1d. Buy sell hold regime context for AI trading signal."New value: +"Candle timeframe, e.g. 1h 4h 1d. Buy sell hold AI trading signal context."

Changed1 schema field changedMay 20, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE",
-  "MEXC",
-  "KUCOIN",
-  "PHEMEX",
-  "BINGX",
-  "HTX",
-  "WEEX",
-  "BITMART",
-  "XT"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE",
+  "MEXC",
+  "KUCOIN",
+  "PHEMEX",
+  "BINGX",
+  "HTX",
+  "WEEX",
+  "BITMART",
+  "XT",
+  "WHITEBIT"
+]

Changed1 schema field changedMay 20, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE",
-  "MEXC",
-  "KUCOIN",
-  "PHEMEX",
-  "BINGX",
-  "HTX"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE",
+  "MEXC",
+  "KUCOIN",
+  "PHEMEX",
+  "BINGX",
+  "HTX",
+  "WEEX",
+  "BITMART",
+  "XT"
+]

Changed1 schema field changedMay 20, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE",
-  "MEXC",
-  "KUCOIN",
-  "PHEMEX"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE",
+  "MEXC",
+  "KUCOIN",
+  "PHEMEX",
+  "BINGX",
+  "HTX"
+]

Changed1 schema field changedMay 20, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE",
-  "MEXC",
-  "KUCOIN"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE",
+  "MEXC",
+  "KUCOIN",
+  "PHEMEX"
+]

Changed1 schema field changedMay 19, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX",
-  "GATE"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE",
+  "MEXC",
+  "KUCOIN"
+]

Changed1 schema field changedMay 19, 2026

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET",
-  "ASTER",
-  "EDGEX"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX",
+  "GATE"
+]

Changed3 schema fields changedMay 16, 2026

changedInput schema / properties / coin / description

Previous value: -"Asset symbol, e.g. 'BTC', 'ETH', 'SOL'"New value: +"Asset symbol — BTC ETH SOL signal. Crypto quant trade call classification."

changedInput schema / properties / exchange / description

Previous value: -"Exchange to analyze. 'HL' = Hyperliquid (default), 'BINANCE' = Binance USDT-M Futures, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M, 'ASTER' = Aster BNB-Chain perp DEX (shadow — experimental), 'EDGEX' = edgeX L2 zk-rollup perp DEX (shadow — experimental). Shadow venues (experimental, not yet on public dashboard) require explicit exchange param; query the mcp://algovault/venues resource for the live per-venue status table."New value: +"Exchange BINANCE HL BYBIT OKX BITGET. Multi-exchange Claude trading agent."

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe"New value: +"Candle timeframe — 1h 4h 1d. Buy sell hold regime context for AI trading signal."

Changed2 schema fields changedMay 16, 2026

changedInput schema / properties / exchange / description

Previous value: -"Exchange to analyze. 'HL' = Hyperliquid (default), 'BINANCE' = Binance USDT-M Futures, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M. Shadow venues (experimental, not yet on public dashboard) require explicit exchange param; query the mcp://algovault/venues resource for the live per-venue status table."New value: +"Exchange to analyze. 'HL' = Hyperliquid (default), 'BINANCE' = Binance USDT-M Futures, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M, 'ASTER' = Aster BNB-Chain perp DEX (shadow — experimental), 'EDGEX' = edgeX L2 zk-rollup perp DEX (shadow — experimental). Shadow venues (experimental, not yet on public dashboard) require explicit exchange param; query the mcp://algovault/venues resource for the live per-venue status table."

changedInput schema / properties / exchange / enum

Previous value: -[
-  "HL",
-  "BINANCE",
-  "BYBIT",
-  "OKX",
-  "BITGET"
-]New value: +[
+  "HL",
+  "BINANCE",
+  "BYBIT",
+  "OKX",
+  "BITGET",
+  "ASTER",
+  "EDGEX"
+]

Changed1 schema field changedMay 16, 2026

changedInput schema / properties / exchange / description

Previous value: -"Exchange to analyze. 'HL' = Hyperliquid (default), 'BINANCE' = Binance USDT-M Futures, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M."New value: +"Exchange to analyze. 'HL' = Hyperliquid (default), 'BINANCE' = Binance USDT-M Futures, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M. Shadow venues (experimental, not yet on public dashboard) require explicit exchange param; query the mcp://algovault/venues resource for the live per-venue status table."

Changed1 schema field changedApr 13, 2026
- addedInput schema / properties / coin / maxLength
```
Added value: +20
```
First observedApr 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read-only, live exchange APIs.' It adds useful behavioral context beyond the annotations: the verdict is composite of trend/ranging and cross-venue funding rate, and the output includes confidence and a strategy hint. It does not cover rate limits or failure modes, but with annotations present the safety profile is sufficiently disclosed.

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 description is two sentences and front-loads the key deliverable: the market regime values, confidence, and strategy hint. The verification sentence is dense but not bloated, and there is no redundant padding.

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?

For a read-only retrieval tool with three well-documented parameters and no output schema, the description supplies the return values, confidence, strategy hint, and composite methodology. It lacks explicit sibling routing and exact response structure, but those gaps are minor given the schema enum coverage and annotations.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds little about the exact parameters beyond limiting the tool to a single crypto perpetual futures asset. It does not add syntax, default semantics, or parameter-specific guidance beyond what the schema already provides.

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 specific verb ('Returns'), the resource ('market regime'), the possible output values, and the asset scope ('crypto perpetual futures'). It does not explicitly differentiate itself from siblings like get_trade_signal or get_trade_call, but the regime-value list makes the core purpose clear.

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?

The context 'for one crypto perpetual futures' implies when the tool is relevant, and 'Read-only, live exchange APIs' clarifies the nature of the call. However, there is no explicit guidance about when to use this tool versus alternatives, and the get_track_record mention is about validating track record rather than choosing between tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AlgoVault — Crypto Quant Trade Calls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

get_market_regime

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources