Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_liquidation_heatmap

Identify support and resistance levels by viewing liquidation clusters across price levels for any coin, revealing potential squeeze zones.

Instructions

Get a liquidation heatmap for any coin. Shows where liquidation clusters are across price levels — essential for identifying support/resistance and potential squeeze zones. Unique data nobody else exposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
coinYesCoin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)
bucketsNoNumber of price buckets in the heatmap
rangeNoPrice range percentage around current price

Implementation Reference

  • src/index.ts:544-565 (registration)
    Registration of the live_liquidation_heatmap tool with the MCP server, including its input schema (coin, buckets, range) and handler that calls the API at /live/liquidation-heatmap/{coin}
    // ══════════════════════════════════════════════════════════
    // TOOL 14: Liquidation Heatmap
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("live_liquidation_heatmap")) server.registerTool(
      "live_liquidation_heatmap",
      {
        description: "Get a liquidation heatmap for any coin. Shows where liquidation clusters are across price levels — essential for identifying support/resistance and potential squeeze zones. Unique data nobody else exposes.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)"),
          buckets: z.number().min(10).max(100).default(50).describe("Number of price buckets in the heatmap"),
          range: z.number().min(1).max(50).default(30).describe("Price range percentage around current price"),
        },
      },
      async ({ useToonFormat, coin, buckets, range }) =>
        toolResult(
          await callAPI(useToonFormat, `/live/liquidation-heatmap/${normalizeCoin(coin)}`, {
            buckets: String(buckets),
            range: String(range),
          })
        )
    );
  • Input schema defining the tool's parameters: coin (required string), buckets (10-100, default 50), range (1-50%, default 30), and optional useToonFormat
    {
      description: "Get a liquidation heatmap for any coin. Shows where liquidation clusters are across price levels — essential for identifying support/resistance and potential squeeze zones. Unique data nobody else exposes.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN (e.g. xyz:SILVER, km:OIL, cash:TSLA)"),
        buckets: z.number().min(10).max(100).default(50).describe("Number of price buckets in the heatmap"),
        range: z.number().min(1).max(50).default(30).describe("Price range percentage around current price"),
      },
  • Handler function that calls the Coinversa public API at /live/liquidation-heatmap/{coin} with buckets and range as query parameters, returning the result formatted as tool content
      async ({ useToonFormat, coin, buckets, range }) =>
        toolResult(
          await callAPI(useToonFormat, `/live/liquidation-heatmap/${normalizeCoin(coin)}`, {
            buckets: String(buckets),
            range: String(range),
          })
        )
    );
Behavior3/5

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

No annotations provided, so description carries full burden. States it's a read operation (Get) with no side effects. Lacks details on return format, rate limits, or authorization needs. Adequate but not fully transparent.

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 sentences, front-loaded with main action, no wasted words. Efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return values more. Mentions 'shows where liquidation clusters are' but lacks details on structure. Adequate given heatmap concept, but could specify response format.

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 description only adds context about heatmap purpose (support/resistance, squeeze zones). No additional parameter details beyond schema. Baseline score of 3 is appropriate.

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?

Clear verb 'Get', specific resource 'liquidation heatmap for any coin', and states what it shows (liquidation clusters across price levels). Distinguishes from siblings like live_liquidation_summary by specifying heatmap format.

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?

Provides context: 'essential for identifying support/resistance and potential squeeze zones'. Implies usage for technical analysis but does not explicitly contrast with alternatives or state when not to use.

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