LiquidVision — Crypto Derivatives Data

get_liquidation_map

Read-onlyIdempotent

[modeled, RISK AHEAD, CEX, now] ESTIMATED open leveraged positions on Binance/Bybit/OKX per price bin at their liquidation price, from candles and open-interest deltas (the CEXs do not publish positions). Current snapshot only; for its evolution over time use get_liquidation_heatmap; for REAL positions use get_hl_liquidation_map (Hyperliquid) or get_lighter_liquidation_map (Lighter); for what already got liquidated use the PAST tools. Returns notional per bin split by leverage tier (5/10/20/25/50/100x) and by exchange, plus cumulative long/short curves from the current price outward. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d. It ranks levels ("if price reaches this level, how much is there": top quarter of traded levels holds ~30-32% of liquidated USD, chance ~24%); it does NOT predict where price will go. Live scoring: get_accuracy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_liquidation_map"
  }
}

Input Schema

Name	Required	Description	Default
`range`	No	Price range around the current price: 12h \| 1d \| 3d \| 7d (and 'max' where stated), the traded range of that window.	1d
`symbol`	Yes	Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).
`exchange`	No	Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it.	all

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / exchange / description

Added value: +"Venue id (binance, bybit, okx, bitget, hyperliquid, gate, htx, kucoin, mexc, bingx, aster, kraken, gmx) or 'all' where the tool allows it."

addedInput schema / properties / range / description

Added value: +"Price range around the current price: 12h | 1d | 3d | 7d (and 'max' where stated), the traded range of that window."

addedInput schema / properties / symbol / description

Added value: +"Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT)."

First observedSep 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say read-only/idempotent; the description carries the substantive burden. It discloses that the CEXs do not publish positions and the numbers are MODELED estimates, tags the payload 'RISK AHEAD, CEX, now', and stays current-snapshot only. That provenance caveat is exactly what an agent needs to avoid treating the output as real position data.

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 capability and provenance line is front-loaded and the sibling routing follows immediately. It is dense with parentheticals and a statistical aside about top-quarter levels, but nearly every clause earns its place.

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?

No output schema exists, and the description compensates by describing the return shape: notional per bin split by leverage tier (5/10/20/25/50/100x) and by exchange, plus cumulative long/short curves outward from current price. It also explains the ranking semantics ('if price reaches this level, how much is there').

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 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?

States a specific resource and derived metric: estimated open leveraged positions per price bin at liquidation price, built from candles and open-interest deltas. It immediately names the sibling tools that serve different needs (get_liquidation_heatmap, get_hl_liquidation_map, get_lighter_liquidation_map), so an agent can place it without opening 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 Guidelines5/5

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

Explicit routing: use this for the current snapshot only, get_liquidation_heatmap for its evolution over time, get_hl_liquidation_map / get_lighter_liquidation_map for REAL positions, and the PAST tools for what already got liquidated. It also states a scope exclusion ('it does NOT predict where price will go') and points to get_accuracy for scoring.

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

All LiquidVision — Crypto Derivatives Data 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.

Resources

Need Help?