Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_liquidation_summary

Get aggregated liquidation summaries over a time window, including event counts, penalty fees, closed PnL, per-coin rollups, and a liquidation timeline for trend analysis.

Instructions

Get an aggregated liquidation summary over a time window. This is the best liquidation tool for summaries, rankings, and trend analysis. Returns event count, penalty fees, closed PnL, per-coin rollups, and a liquidation timeline.

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)

Implementation Reference

  • Handler for live_liquidation_summary: calls API endpoint /live/risk/liquidations/summary with optional 'since' and 'coin' parameters.
      async ({ useToonFormat, since, coin }) => {
        const params: Record<string, string> = { since };
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, "/live/risk/liquidations/summary", params));
      }
    );
  • Input schema for live_liquidation_summary: accepts useToonFormat (bool, default true), since (time window, default '7d'), and optional coin filter.
    "live_liquidation_summary",
    {
      description: "Get an aggregated liquidation summary over a time window. This is the best liquidation tool for summaries, rankings, and trend analysis. Returns event count, penalty fees, closed PnL, per-coin rollups, and a liquidation timeline.",
      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)"),
      },
    },
  • src/index.ts:666-681 (registration)
    Registration of the live_liquidation_summary tool using server.registerTool(). The tool is conditionally registered based on API key (not in FREE_TIER_TOOLS).
    if (shouldRegister("live_liquidation_summary")) server.registerTool(
      "live_liquidation_summary",
      {
        description: "Get an aggregated liquidation summary over a time window. This is the best liquidation tool for summaries, rankings, and trend analysis. Returns event count, penalty fees, closed PnL, per-coin rollups, and a liquidation timeline.",
        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)"),
        },
      },
      async ({ useToonFormat, since, coin }) => {
        const params: Record<string, string> = { since };
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, "/live/risk/liquidations/summary", params));
      }
    );
Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses the aggregated nature and return fields, but does not mention side effects, rate limits, or authorization needs. The read-only behavior is implied but not explicit.

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?

Two succinct sentences: first defines purpose and scope, second lists returns and recommends usage. No filler or redundant information.

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?

No output schema exists, so the description adequately explains return fields. It positions itself among siblings but lacks explicit mentions of alternatives. Coverage of parameters and returns is sufficient for most use cases.

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% with descriptions for all parameters. The description adds little beyond the schema, only implying that 'per-coin rollups' relate to the coin parameter. Matches baseline for high coverage.

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 it 'Get[s] an aggregated liquidation summary over a time window' and lists specific outputs (event count, penalty fees, etc.). It distinguishes from siblings like live_liquidation_heatmap and live_recent_liquidations by positioning itself for summaries, rankings, and trend analysis.

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 explicitly says 'This is the best liquidation tool for summaries, rankings, and trend analysis,' guiding when to use it. However, it does not explicitly mention when not to use it or name alternatives like live_recent_liquidations for individual events.

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