LiquidVision — Crypto Derivatives Data

get_liquidations

[measured, PAST] Individual liquidation ORDERS that already happened (side, price, qty), newest first, at most limit rows (max 2000). This is the raw feed: use it when you need the orders themselves. For totals use get_liquidations_summary; for cascades as events use get_liquidation_cascades; for where OPEN positions would be liquidated use a *_liquidation_map tool. Market-wide, 500 rows is only a few minutes of a busy hour: pass symbol (BTCUSDT) and/or min_usd to look further back. side=long means a long position was liquidated.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`symbol`	No
`min_usd`	No
`minutes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 500,
+  "title": "Limit",
+  "type": "integer"
+}

addedInput schema / properties / min_usd

Added value: +{
+  "default": 0,
+  "title": "Min Usd",
+  "type": "number"
+}

addedInput schema / properties / symbol

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Symbol"
+}

First observedSep 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose ordering, the max-2000 row cap, the default-500 coverage warning ('only a few minutes of a busy hour'), and the side=long sign convention. It does not cover auth requirements, rate limits, or what happens at the 2000-row boundary, so it falls short of complete behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core definition before alternatives, then the operational caveat and filter advice. Dense but every clause carries distinct information; nothing is redundant with the schema or restates the tool name.

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?

An output schema exists, so return-value explanation is rightly omitted, and the safety profile is empty (a read-only feed) so no annotation detail is missing. The only shortfall is the unaddressed `minutes` parameter, which is the one thing an agent would still have to guess at.

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 0%, so the description must compensate, and it explains limit (capped at 2000), symbol (BTCUSDT example), and min_usd (used to reach further back). The fourth parameter, `minutes`, is never mentioned, leaving a real semantics gap for a defaulted time window.

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 verb and resource (individual liquidation orders that already happened) plus the per-row fields (side, price, qty), ordering (newest first), and cap. It positively distinguishes itself from get_liquidations_summary, get_liquidation_cascades, and the *_liquidation_map family, so an agent can route 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 when-to-use ('use it when you need the orders themselves') paired with three named alternatives for related-but-different needs (totals, cascades, hypothetical liquidation zones). It also gives practical narrowing advice ('pass symbol and/or min_usd to look further back') tied to the market-wide coverage caveat.

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?