Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Crypto liquidations: daily long/short totals per symbol and exchange

get_liquidations
Read-only

Query daily long and short crypto futures liquidation totals in USD per symbol and exchange to analyze how much was liquidated or which side was flushed.

Instructions

Call this when the user asks how much was liquidated in crypto futures, whether longs or shorts got flushed, or for liquidation history. Returns daily long and short liquidation totals in USD per symbol and exchange, recorded from ByKaranteli's own stream collectors on every liquidation venue it counts, listed on bykaranteli.com/coverage (recorded events, a floor, not estimates). One row per finalized UTC day, symbol and exchange; history begins 2026-07-30 and grows daily. Without symbol, rows holds the first 30 rows (newest day, largest first) while summary covers every matching row; pass symbol or limit (up to 400) for more rows.

Input Schema

NameRequiredDescriptionDefault
daysNoHow many most recent days to return (default 7).
limitNoOptional. Rows to return, newest day first and largest first within a day (default 30 without symbol, 400 with one).
symbolNoOptional symbol filter like BTCUSDT or ETHUSDT. Omit for all symbols.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.36.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional. Rows to return, newest day first and largest first within a day (default 30 without symbol, 400 with one).",
+  "maximum": 400,
+  "minimum": 1,
+  "type": "integer"
+}
  3. First observedv0.5.0

TDQS

A4.7/5.0
Behavior5/5

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

With readOnlyHint and openWorldHint already set, the description adds substantial behavioral context: the data comes from own stream collectors, represents recorded events as a floor rather than estimates, covers a list of venues on a coverage page, starts at a specific date, and grows daily. It also clarifies the rows-versus-summary behavior, which is important for interpreting results.

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 front-loaded with the primary use case and return shape. It is dense but every sentence earns its place by covering provenance, limitations, granularity, history start, and pagination behavior.

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 read-only query tool with no output schema, the description explains the return structure (daily long/short totals per symbol and exchange), the rows versus summary distinction, the history start date, and how to expand results. Nothing essential is missing for correct invocation.

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%, so the schema already documents default limits and ordering. The description adds useful meaning beyond the schema by explaining that without a symbol the rows array holds the first 30 rows while summary covers every matching row, and that passing symbol or limit returns more rows.

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 states a specific verb and resource: it returns daily long and short liquidation totals in USD per symbol and exchange. The granularity (one row per finalized UTC day, symbol, exchange) clearly distinguishes it from sibling tools like get_liquidation_cascades, get_liquidation_leaderboard, and get_liqmap, even without naming them explicitly.

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?

It gives a clear triggering condition: call this when the user asks how much was liquidated, whether longs or shorts got flushed, or for liquidation history. It also explains how to get more rows via symbol or limit. However, it does not explicitly say when to prefer a sibling such as get_liquidation_cascades or get_liquidation_leaderboard instead.

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

Deploy Server

Other Tools