Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_recent_liquidations

Retrieve real liquidation events with wallet, coin, penalty fee, and closed PnL. Filter by time window, coin, and limit for precise analysis of forced unwind activity.

Instructions

Get real liquidation events from the syncer. Best for questions like 'where did forced unwind activity actually hit?' or 'show me BTC liquidations over the last 30 days'. Returns wallet, coin, penalty fee, and closed PnL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
sinceNoTime window: e.g. '10m' (minutes), '1h' (hours), '1d' (days)7d
coinNoOptional coin filter (e.g. BTC, ETH, SOL or builder dex prefix:COIN)
limitNoNumber of liquidation events to return

Implementation Reference

  • Handler function for live_recent_liquidations tool. Takes useToonFormat, since, coin, and limit params. Builds query params and calls the API at /live/risk/liquidations/recent. The normalized coin filter is conditionally added.
      async ({ useToonFormat, since, coin, limit }) => {
        const params: Record<string, string> = { since, limit: String(limit) };
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, "/live/risk/liquidations/recent", params));
      }
    );
  • Input schema for live_recent_liquidations. Defines useToonFormat (boolean, default true), since (time window string like '7d'), coin (optional string for filtering), and limit (number 1-200, default 50).
    {
      description: "Get real liquidation events from the syncer. Best for questions like 'where did forced unwind activity actually hit?' or 'show me BTC liquidations over the last 30 days'. Returns wallet, coin, penalty fee, and closed PnL.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        since: sinceSchema.default("7d"),
        coin: z.string().optional().describe("Optional coin filter (e.g. BTC, ETH, SOL or builder dex prefix:COIN)"),
        limit: z.number().min(1).max(200).default(50).describe("Number of liquidation events to return"),
      },
    },
  • src/index.ts:645-661 (registration)
    Registration of the live_recent_liquidations tool via server.registerTool(). Conditionally registered based on shouldRegister() guard. The tool is NOT in the FREE_TIER_TOOLS set so it requires an API key.
    if (shouldRegister("live_recent_liquidations")) server.registerTool(
      "live_recent_liquidations",
      {
        description: "Get real liquidation events from the syncer. Best for questions like 'where did forced unwind activity actually hit?' or 'show me BTC liquidations over the last 30 days'. Returns wallet, coin, penalty fee, and closed PnL.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          since: sinceSchema.default("7d"),
          coin: z.string().optional().describe("Optional coin filter (e.g. BTC, ETH, SOL or builder dex prefix:COIN)"),
          limit: z.number().min(1).max(200).default(50).describe("Number of liquidation events to return"),
        },
      },
      async ({ useToonFormat, since, coin, limit }) => {
        const params: Record<string, string> = { since, limit: String(limit) };
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, "/live/risk/liquidations/recent", params));
      }
    );
Behavior3/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states 'real liquidation events from the syncer' and what is returned, which implies a read-only, real-time operation. However, it does not explicitly mention idempotency, rate limits, or data freshness.

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 two sentences with a clear purpose, example usage, and output fields. Every sentence is valuable and no filler exists.

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?

The description covers purpose, usage context, and output fields. Without an output schema, it adequately explains returns. It lacks explicit mention of error conditions or required permissions, which are minor in this context.

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%, and the description does not add significant meaning beyond the schema. For example, the 'since' parameter is described similarly. The description's listing of returned fields does not directly enhance parameter understanding.

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 clearly states the tool retrieves real liquidation events, provides specific example queries, and lists returned fields (wallet, coin, penalty fee, closed PnL). It effectively distinguishes from sibling tools like live_liquidation_heatmap and live_liquidation_summary by focusing on raw events.

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 best-use examples ('where did forced unwind activity actually hit?', 'show me BTC liquidations over the last 30 days'), implying the tool is for raw event queries. However, it does not explicitly exclude aggregated views or comparison to siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coinversaa/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server