AgentFeed

Recent liquidations

get_recent_liquidations

Read-onlyIdempotent

Recent perp liquidations across Bybit (complete unthrottled tape), OKX and Binance: timestamp, long/short, size, price, USD value. Any USDT perp we record, not just majors. Costs 0.003 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	max rows, 1-100, default 25
`scope`	No	core = the 5 majors (default), all = every recorded USDT perp
`symbol`	No	SOL, BTC, ETH, XRP, DOGE, or any USDT perp e.g. SXTUSDT (omit for majors)
`min_usd`	No	only prints >= this USD size

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_recent_liquidations payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_recent_liquidations
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_recent_liquidations payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_recent_liquidations",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_recent_liquidations",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds important behavioral context beyond annotations: the call costs 0.003 USDC via x402 on Solana or Base, and the data is described as a 'complete unthrottled tape' covering all recorded USDT perps. This is genuinely useful operational information.

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 tight sentences, each earning its place: data sources and output fields, full perp coverage, and cost/payment rail. No filler or redundancy; the most important distinguishing detail—complete unthrottled tape across venues—is front-loaded.

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?

With an output schema present, annotations covering the safety profile, and all parameters documented in the input schema, the description is complete enough. It adds the critical missing operational detail (cost and payment method) and clearly states the tool's scope relative to the broader tool family.

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?

The input schema already documents all four parameters with 100% coverage, so the description does not need to add much. It reinforces the 'not just majors' concept that maps to the scope and symbol parameters, but it does not add meaningful detail beyond the schema's own descriptions.

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?

The description names a specific resource—recent perp liquidations across Bybit, OKX, and Binance—and specifies the exact fields returned. It also differentiates itself from sibling liquidation tools by emphasizing the 'complete unthrottled tape' and coverage of 'any USDT perp, not just majors.'

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

Usage Guidelines4/5

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

The description gives clear context for when this tool is appropriate: when the user needs a full, unthrottled recent liquidation tape across multiple venues, including non-major perps. It does not explicitly name alternatives or state when not to use it, but the scope is clear enough for an agent to route correctly.

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

All AgentFeed 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.