whale-data

Recent liquidations

liquidations

Read-onlyIdempotent

Liquidation trades for a pair with the long and short breakdown, live tape merged with the recorded series so a restart never erases history. A long is force-closed by selling, so sell-side events are long liquidations. long_liquidations and short_liquidations are event COUNTS; long_usd and short_usd carry the dollar split. Pass hours to ask for a period (hours: 24 for today); without it you get the most recent rows and window_minutes tells you how far back they reach. truncated:true means more events matched than were returned, so window_minutes covers the returned rows only and total_in_window has the real count. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Alias for pair.
`pair`	No	e.g. ETH/USD. A bare symbol like ETH also works.
`hours`	No	Look back this many hours, up to 720. Omit for the most recent events.
`limit`	No	Max rows returned. Capped at 25 on the free plans and 1000 on a paid plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless.
`since_ms`	No	Polling cursor: only rows newer than this Unix-ms timestamp, applied before the row cap. Pass back the next_since_ms from the previous answer so a timer never re-reads the same rows.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`pair`	No	The pair these events belong to.
`count`	No	How many events fired in the whole window, not how many rows came back.
`capped`	No	Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
`sources`	No	How the events split between the streamed exchanges and Hyperliquid, and whether the Hyperliquid part is a sample.
`long_usd`	No	Dollars of longs force-closed across the window.
`available`	No	False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
`short_usd`	No	Dollars of shorts force-closed across the window.
`truncated`	No	True when more rows matched than were returned, so what you have is a page and not the whole set.
`access_note`	No	What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
`liquidations`	No	The events themselves, newest first: price, size in base and quote, side (long_liquidated or short_liquidated), exchange and time. A sample of the window when truncated is true.
`window_hours`	No	The period the totals cover, in hours.
`rows_returned`	No	How many event rows are actually in this reply.
`window_minutes`	No	The same period in minutes.
`requested_hours`	No	The period asked for, so a page can be told apart from a period.
`total_in_window`	No	How many events the window holds in total.
`history_included`	No	True when the recorded series was merged in, so a restart has not erased earlier events.
`total_volume_usd`	No	Dollars forced out across the whole window.
`long_liquidations`	No	COUNT of longs force-closed. For dollars read long_usd.
`rows_span_minutes`	No	How far back the returned rows themselves reach.
`short_liquidations`	No	COUNT of shorts force-closed. For dollars read short_usd.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / limit / description

Previous value: -"Max rows returned. Capped at 25 keyless and 1000 on a paid plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."New value: +"Max rows returned. Capped at 25 on the free plans and 1000 on a paid plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / since_ms

Added value: +{
+  "description": "Polling cursor: only rows newer than this Unix-ms timestamp, applied before the row cap. Pass back the next_since_ms from the previous answer so a timer never re-reads the same rows.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / limit / description

Previous value: -"Max rows returned. Capped at 25 keyless and 1000 on a developer plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."New value: +"Max rows returned. Capped at 25 keyless and 1000 on a paid plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / limit / description

Previous value: -"Max rows returned. Capped at 50 keyless and 1000 on a developer plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."New value: +"Max rows returned. Capped at 25 keyless and 1000 on a developer plan; asking for more returns the cap, and the payload says so in `capped`. count and the *_usd totals always cover the whole window regardless."

Changed1 schema field changedAug 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "access_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
+    },
+    "available": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess."
+    },
+    "capped": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "applied": {
+              "description": "The value actually used.",
+              "type": "number"
+            },
+            "argument": {
+              "description": "Which argument was cut down, for example limit or hours.",
+              "type": "string"
+            },
+            "by": {
+              "description": "Why it was cut: keyless for the free ceiling, plan_max for a paid ceiling, tool_max for a ceiling no plan raises.",
+              "type": "string"
+            },
+            "max": {
+              "description": "The ceiling that applied.",
+              "type": "number"
+            },
+            "requested": {
+              "description": "The value the caller asked for.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "argument",
+            "requested",
+            "applied",
+            "max",
+            "by"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit."
+    },
+    "count": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many events fired in the whole window, not how many rows came back."
+    },
+    "history_included": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "True when the recorded series was merged in, so a restart has not erased earlier events."
+    },
+    "liquidations": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The events themselves, newest first: price, size in base and quote, side (long_liquidated or short_liquidated), exchange and time. A sample of the window when truncated is true."
+    },
+    "long_liquidations": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "COUNT of longs force-closed. For dollars read long_usd."
+    },
+    "long_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Dollars of longs force-closed across the window."
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading."
+    },
+    "pair": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The pair these events belong to."
+    },
+    "requested_hours": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The period asked for, so a page can be told apart from a period."
+    },
+    "rows_returned": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many event rows are actually in this reply."
+    },
+    "rows_span_minutes": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How far back the returned rows themselves reach."
+    },
+    "short_liquidations": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "COUNT of shorts force-closed. For dollars read short_usd."
+    },
+    "short_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Dollars of shorts force-closed across the window."
+    },
+    "sources": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How the events split between the streamed exchanges and Hyperliquid, and whether the Hyperliquid part is a sample."
+    },
+    "total_in_window": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many events the window holds in total."
+    },
+    "total_volume_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Dollars forced out across the whole window."
+    },
+    "truncated": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "True when more rows matched than were returned, so what you have is a page and not the whole set."
+    },
+    "window_hours": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The period the totals cover, in hours."
+    },
+    "window_minutes": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The same period in minutes."
+    }
+  },
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description reveals meaningful behavior: history survives restarts, sell-side events are always long liquidations, counts are event counts rather than dollars, and truncated results affect only returned rows. None of this is available from annotations or the input schema, and it does not contradict the annotations.

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?

The description is dense but every sentence earns its place: purpose, methodology, field semantics, parameter default, truncation caveat, and a final scope guard. It is front-loaded with the core behavior and avoids repeating the schema verbatim.

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?

For a pair-scoped read-only data tool with an output schema, this is complete: it covers the default window, the truncation semantics, and clarifies the long vs short dollar split ahead of the output schema. The annotations already cover safety, and the schema covers parameter formats, so nothing needed for correct invocation is missing.

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% and the schema already documents coin/pair, hours, limit, and since_ms. The description adds useful semantics beyond that, especially the hours default ('hours: 24 for today'), what happens when hours is omitted, and the meaning of window_minutes and truncation; it does not deeply expand every parameter, so a 4 rather than a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens by naming the resource and scope ('Liquidation trades for a pair with the long and short breakdown'), so an agent can tell it is pair-scoped rather than market-wide. It is not a tautology and conveys the live-plus-recorded merge, but it never names sibling tools such as market_liquidations or coin_liquidations to differentiate them.

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

Usage Guidelines2/5

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

It explains parameter-driven behavior ('Pass hours... without it...') and adds the caveat 'Descriptive market data only', but it gives no guidance on when to choose this tool over any of the many liquidation/market sibling tools. No alternative is named and no exclusion condition is stated.

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

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