AlgoVault — Crypto Quant Trade Calls

get_trade_signal

Read-only

Returns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures. One asset only; whole-market scan: scan_trade_calls. Read-only: live exchange APIs, no orders. Verified track record: get_track_record or performance://signal-performance; on-chain verified merkle anchor. [ALIAS] This tool is an alias of get_trade_call — same behavior, kept for backward compatibility. Prefer get_trade_call for new integrations.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	Yes	Base asset, e.g. BTC ETH SOL signal, or a US stock/ETF ticker (no USDT).
`exchange`	No	Crypto venue (default Binance), e.g. Binance Bybit OKX Bitget Hyperliquid.
`timeframe`	No	Candle timeframe, 1m to 1d. Default 15m. Crypto quant intraday horizon.
`assetClass`	No	Force engine: 'perp' or 'equity'. Cross-venue multi-exchange AI trading signal.
`includeReasoning`	No	Include reasoning: trend ranging crypto signal and market regime drivers.

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"
+]

Changed5 schema fields changedJun 17, 2026

changedInput schema / properties / assetClass / description

Previous value: -"Force engine: 'perp' or 'equity'. MCP tool for trading — AI trading signal."New value: +"Force engine: 'perp' or 'equity'. Cross-venue multi-exchange AI trading signal."

changedInput schema / properties / coin / description

Previous value: -"Ticker — crypto signal (BTC ETH SOL signal) or a US stock/ETF ticker."New value: +"Base asset, e.g. BTC ETH SOL signal, or a US stock/ETF ticker (no USDT)."

changedInput schema / properties / exchange / description

Previous value: -"Crypto venue, default Binance — cross-venue multi-exchange perp routing."New value: +"Crypto venue (default Binance), e.g. Binance Bybit OKX Bitget Hyperliquid."

changedInput schema / properties / includeReasoning / description

Previous value: -"Include reasoning for the trade call verdict (regime, trend ranging signals)."New value: +"Include reasoning: trend ranging crypto signal and market regime drivers."

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe (1m to 1d) for crypto quant agents. Default 15m intraday."New value: +"Candle timeframe, 1m to 1d. Default 15m. Crypto quant intraday horizon."

Changed5 schema fields changedJun 9, 2026

addedInput schema / properties / assetClass

Added value: +{
+  "description": "Force engine: 'perp' or 'equity'. MCP tool for trading — AI trading signal.",
+  "enum": [
+    "perp",
+    "equity"
+  ],
+  "type": "string"
+}

changedInput schema / properties / coin / description

Previous value: -"Asset — BTC ETH SOL signal for crypto perpetual futures or TradFi symbol."New value: +"Ticker — crypto signal (BTC ETH SOL signal) or a US stock/ETF ticker."

removedInput schema / properties / exchange / default
```
Removed value: -"BINANCE"
```

changedInput schema / properties / exchange / description

Previous value: -"Exchange — 'BINANCE' = Binance USDT-M Futures (default), HL/BYBIT/OKX/BITGET."New value: +"Crypto venue, default Binance — cross-venue multi-exchange perp routing."

removedInput schema / properties / timeframe / default
```
Removed value: -"15m"
```

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"
+]

Changed4 schema fields changedMay 16, 2026

changedInput schema / properties / coin / description

Previous value: -"Asset symbol, e.g. 'ETH', 'BTC', 'SOL'"New value: +"Asset — BTC ETH SOL signal for crypto perpetual futures or TradFi symbol."

changedInput schema / properties / exchange / description

Previous value: -"Exchange to analyze. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, '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. Asset availability varies per venue — pass exchange explicitly to target a specific venue."New value: +"Exchange — 'BINANCE' = Binance USDT-M Futures (default), HL/BYBIT/OKX/BITGET."

changedInput schema / properties / includeReasoning / description

Previous value: -"Include human-readable reasoning"New value: +"Include reasoning for the trade call verdict (regime, trend ranging signals)."

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe. 1m/3m for HFT scalping, 5m/15m for intraday agents (most popular), 30m/1h/2h for swing, 4h/8h/12h/1d for position trading. Free tier: all 11 timeframes available, 100 calls/month."New value: +"Candle timeframe (1m to 1d) for crypto quant agents. Default 15m intraday."

Changed2 schema fields changedMay 16, 2026

changedInput schema / properties / exchange / description

Previous value: -"Exchange to analyze. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, '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. Asset availability varies per venue — pass exchange explicitly to target a specific venue."New value: +"Exchange to analyze. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, '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. Asset availability varies per venue — pass exchange explicitly to target a specific venue."

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. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M. Asset availability varies per venue — pass exchange explicitly to target a specific venue."New value: +"Exchange to analyze. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, '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. Asset availability varies per venue — pass exchange explicitly to target a specific venue."

Changed3 schema fields changedMay 15, 2026

changedInput schema / properties / exchange / default
```
Previous value: -"HL"New value: +"BINANCE"
```

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. 'BINANCE' = Binance USDT-M Futures (default), 'HL' = Hyperliquid, 'BYBIT' = Bybit Linear, 'OKX' = OKX Swap, 'BITGET' = Bitget USDT-M. Asset availability varies per venue — pass exchange explicitly to target a specific venue."

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe. All Hyperliquid intervals supported. 1m/3m for HFT scalping, 5m/15m for intraday agents (most popular), 30m/1h/2h for swing, 4h/8h/12h/1d for position trading. Free tier: all 11 timeframes available, 100 calls/month."New value: +"Candle timeframe. 1m/3m for HFT scalping, 5m/15m for intraday agents (most popular), 30m/1h/2h for swing, 4h/8h/12h/1d for position trading. Free tier: all 11 timeframes available, 100 calls/month."

Changed1 schema field changedApr 30, 2026

changedInput schema / properties / timeframe / description

Previous value: -"Candle timeframe. All Hyperliquid intervals supported. 1m/3m for HFT scalping, 5m/15m for intraday agents (most popular), 30m/1h/2h for swing, 4h/8h/12h/1d for position trading. Free tier: 15m and 1h only."New value: +"Candle timeframe. All Hyperliquid intervals supported. 1m/3m for HFT scalping, 5m/15m for intraday agents (most popular), 30m/1h/2h for swing, 4h/8h/12h/1d for position trading. Free tier: all 11 timeframes available, 100 calls/month."

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

TDQS

A4.5/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; the description adds that it queries 'live exchange APIs, no orders', discloses alias equivalence with get_trade_call, and mentions a verified track record. This adds useful behavioral context beyond annotations, though it could detail latency or failure modes.

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 main output is front-loaded in the first sentence. Subsequent sentences each serve a purpose: scope, whole-market alternative, read-only safety, verification, and alias. It is dense but not bloated; the 'performance://signal-performance' reference is slightly cryptic but still earns its place.

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 tool with five parameters, no output schema, and informative annotations, the description covers the return shape (BUY/SELL/HOLD, confidence, market regime), single-asset input, read-only behavior, and alias relationship. It could add default exchange/timeframe behavior or response structure details, but the current context is sufficient for correct invocation.

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?

Input schema coverage is 100%, so the baseline is already satisfied. The description adds meaning by clarifying 'One asset only' and 'crypto or tokenized-stock perpetual futures', which usefully constrains the coin and assetClass parameters beyond the schema examples.

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?

Description opens with a specific verb and resource: 'Returns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures.' It explicitly distinguishes itself from scan_trade_calls ('One asset only; whole-market scan') and identifies the alias get_trade_call, so sibling confusion is minimized.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states single-asset scope and routes whole-market scans to scan_trade_calls. It also points to get_track_record/performance://signal-performance for verification and advises preferring get_trade_call for new integrations, giving clear when-to-use and alternative guidance.

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_trade_signal

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources