Skip to main content
Glama

Hyperliquid Liquidation Heatmap – Crypto Trading – by HyperPerps

Hyperliquid liquidation heatmap

get_liquidation_heatmap
Read-only

Live liquidation clusters (long and short walls with prices, notional, distance from spot), stop-loss and take-profit pools, and positioning stats for a Hyperliquid perp, computed from ~100k tracked wallets and refreshed every ~15 s. Default view: walls within 5% of spot, biggest per side; range/levels widen it to the full ladder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_liquidation_heatmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNo% band around spot to include, e.g. '25', or 'all'
levelsNomax walls per side, biggest first, e.g. '50', or 'all'
symbolYesPerp ticker: BTC, ETH, SOL, HYPE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the genuinely useful behavioral facts: computed from ~100k tracked wallets, refreshed roughly every 15 seconds, and what the default truncation is. That staleness/coverage context goes meaningfully beyond the annotations, though it does not warn about latency or data gaps.

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?

Two dense sentences, no filler; the payload contents come first and the default-view behavior second. The first sentence is a long parenthetical list but each item earns its place.

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?

With no output schema, the description carries the burden of describing returns, and it enumerates the cluster fields (price, notional, distance from spot) plus the extra pools and stats. Missing only response shaping details such as ordering guarantees or error behavior for an unsupported symbol.

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 description coverage is 100%, so the baseline is 3. The description does add the default values (5% band, biggest per side) that the schema does not state, which is marginal added meaning over the schema's examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — live liquidation clusters, stop-loss/take-profit pools, and positioning stats for a Hyperliquid perp — plus the data provenance and refresh cadence. It does not, however, explicitly distinguish itself from the sibling get_heatmap_field_definitions, so an agent must infer that one describes fields and this one returns data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that the default view is walls within 5% of spot and biggest per side, and that range/levels widen to the full ladder — that is usage guidance for the parameters. There is no explicit when-to-use/when-not guidance or routing to an alternative tool.

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.