LiquidVision — Crypto Derivatives Data

get_liquidations

Recent liquidation events (side, price, qty), NEWEST FIRST, at most limit rows (max 2000). Market-wide, 500 rows is only a few minutes of a busy hour: pass symbol (BTCUSDT) and/or min_usd to look further back, or use get_liquidations_summary for totals and get_history for the archive. 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 does well: it discloses ordering (newest first), a hard row cap (max 2000), the event shape, and the non-obvious semantics of side=long. It omits any mention of the `minutes` window or auth/rate-limit behavior, which are the remaining behavioral gaps for a no-annotation tool.

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?

Three dense sentences with the core scope constraint front-loaded before the routing advice. No filler; every clause either defines scope, semantics, or the alternative tool.

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 values need not be explained, and the description covers scope, ordering, narrowing, and alternatives. It is nearly complete, with the sole gap being the undocumented `minutes` window parameter.

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. It adds real meaning for `limit` (max 2000), `symbol` (BTCUSDT example), and `min_usd` (used to look further back), but says nothing about `minutes`, leaving one of four parameters undocumented in both schema and prose.

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 ('Recent liquidation events') plus the return shape (side, price, qty) and ordering (NEWEST FIRST). It names the sibling tools it is not (get_liquidations_summary, get_history), so an agent can distinguish its role without opening other schemas.

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?

Explicitly states when to narrow scope ('pass symbol and/or min_usd to look further back') and which alternatives to pick instead for totals or archive access. The note that market-wide 500 rows is 'only a few minutes of a busy hour' gives concrete guidance on when the default is insufficient.

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?