Skip to main content
Glama

Liquidations: where positions are force-closed

liquidations
Read-only

Coins with the largest liquidations in the last hour or 24 hours, exchanges summed, with the long/short split (longShare ≥ 0.6 — longs are being wiped out, ≤ 0.4 — shorts). Read together with an extreme funding rate it shows a squeeze in progress. Coverage: exchange liquidation streams of Binance, OKX, Bitget, Gate, Aster and part of Bybit; Hyperliquid and Bitunix are not covered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "liquidations"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the summary and links: 'en' (default) or 'ru'
limitNoCoins, default 10
windowNoTime window, default 1h

Output Schema

NameRequiredDescriptionDefault
dataYesCompact numbers the conclusion is based on, units named inside
linkYesLive page with the same data
summaryYesOne-line conclusion — quote this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint already declares the safety profile, and the description adds genuinely useful context the annotation cannot carry: the longShare ≥ 0.6 / ≤ 0.4 interpretation and the exact coverage boundary (Binance, OKX, Bitget, Gate, Aster, part of Bybit; Hyperliquid and Bitunix excluded). It does not mention update cadence or rate limits, but with an output schema present and annotations covering safety, that is a minor gap.

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 core definition is front-loaded in the first sentence and the interpretive guidance follows naturally. The coverage sentence is long but every clause (which exchanges count, which do not) prevents a wrong conclusion, so it earns its space.

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?

For a read-only ranking tool with a full output schema, this covers what an agent needs: metric definition, aggregation, window options, threshold semantics, and the coverage caveat that would otherwise cause false negatives. Only update frequency and data latency are left unstated.

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 coverage is 100%, so lang, limit, and window are fully documented in the schema itself. The description mentions the two windows inline but adds no format, default, or sizing guidance for limit or lang, so the baseline of 3 applies.

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?

"Coins with the largest liquidations in the last hour or 24 hours, exchanges summed" gives a specific resource (liquidation ranking), the metric, the aggregation rule, and both time windows. It is clearly distinct from siblings like funding_events or delistings, so an agent can identify it without opening the schema.

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?

"Read together with an extreme funding rate it shows a squeeze in progress" tells the agent when this tool is most informative and implies pairing it with funding tools. It stops short of naming an alternative tool explicitly or stating when not to use it, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources