LiquidVision — Crypto Derivatives Data

get_liquidation_heatmap

Read-onlyIdempotent

[modeled, RISK AHEAD, CEX, over time] The same estimated CEX map as get_liquidation_map but as a time series: grid[t][b] is the estimated USD of leveraged positions with their liquidation price in price bin b at time cols[t] (ms), bins[b] the bin's centre price (240 bins fitted to the traded range), price[t] the close. A level disappears once price trades through it. Call this only to see WHEN a cluster formed and whether it survived; for the current picture call get_liquidation_map (far smaller answer, split by leverage and exchange). The answer is large (about 35,000 numbers). symbol: BASEUSDT. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d.

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_heatmap"
  }
}

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 already cover read-only/idempotent safety, but the description adds things annotations cannot: the data is modeled/estimated, response size is about 35,000 numbers, and levels vanish once price trades through them. That last point materially changes how an agent should interpret historical cells.

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?

Dense but front-loaded and free of filler; the bracketed tag line and payload-shape sentence earn their place. Minor cost: the bracket notation and the trailing parameter crib sheet read tersely and could be split for scanability.

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?

There is no output schema, so the description must carry the return contract — and it does, via grid/bins/price/cols semantics plus a size warning. Combined with the sibling pointer and parameter constraints, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description contributes practical narrowing: exchange is effectively all|binance|bybit|okx here (a subset of the schema's 13-venue enum), and range is limited to 12h|1d|3d|7d. Symbol format (BASEUSDT) is also restated usefully, though it duplicates the schema.

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?

Names a specific resource and form ('the same estimated CEX map as get_liquidation_map but as a time series') and defines the returned structure explicitly (grid[t][b], bins, price, cols). An agent can distinguish it from get_liquidation_map and get_liquidation_cascades without opening the 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?

Gives an explicit when-to-use ('only to see WHEN a cluster formed and whether it survived') and names the alternative with the condition that selects it ('for the current picture call get_liquidation_map'), including a cost tradeoff ('far smaller answer'). This is a textbook routing instruction.

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?