Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Liquidation leaderboard

get_liquidation_leaders
Read-onlyIdempotent

What is blowing up RIGHT NOW: top symbols ranked by liquidation USD across every USDT perp we record on Bybit, OKX and Binance. Per symbol: total liquidated, long vs short split, biggest single print, venue count, dominant side. The fastest read on where leverage is being flushed. Costs 0.02 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNotop N symbols, 1-50, default 10
window_minNolookback minutes, 5-1440, default 60

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_liquidation_leaders payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_liquidation_leaders
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_liquidation_leaders payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_liquidation_leaders",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_liquidation_leaders",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable context beyond annotations: cross-venue data sources, the aggregation fields returned, and the 0.02 USDC fee with settlement rails. No contradictory behavioral claims are present.

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?

The description is compact and front-loaded, leading with the core purpose, then listing output fields, positioning, and cost. The rhetorical phrases like 'blowing up RIGHT NOW' and 'fastest read' add tone but not hard information, which keeps it from a perfect score.

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 low-complexity read-only tool with an output schema and two optional, well-documented parameters, the description provides everything needed: source venues, per-symbol result dimensions, and the fee. Nothing an agent needs to call it correctly is clearly missing.

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 100%, and both parameters (limit, window_min) already have clear descriptions in the schema. The tool description does not add further parameter nuance, but the schema carries the semantic weight.

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 clearly identifies the resource: top symbols ranked by liquidation USD across USDT perps on Bybit, OKX, and Binance, with per-symbol breakdown fields. It is unambiguous about what the tool returns, though it does not explicitly contrast itself with closely related siblings like get_liquidation_stats or get_recent_liquidations.

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 phrase 'fastest read on where leverage is being flushed' gives an agent a clear context for when to use this tool: quick liquidation-pulse monitoring. It does not spell out exclusions or alternatives, but for a simple read-only snapshot tool the implied usage is reasonably clear.

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

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