Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Liquidation Heatmap

tape_liquidation_heatmap
Read-onlyIdempotent

Observed liquidation price levels for BTC, ETH, SOL or HYPE: where open positions of the largest wallets would liquidate, bucketed by price, with realized liquidations on the same axis and the share of open interest observed. Not a forecast. CONCISE (default) returns the densest levels and coverage in a few hundred tokens; DETAILED returns the full grid. Result carries provenance. For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated with Hyperliquid Labs or the Hyperliquid Foundation.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "BTC",
      "timeframe": "24h",
      "response_format": "CONCISE"
    },
    "name": "tape_liquidation_heatmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoMarket (default BTC).
timeframeNoHistory span (default 24h).
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "coin": "BTC",
      +    "response_format": "CONCISE",
      +    "timeframe": "24h"
      +  }
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully adds that results are not a forecast, that CONCISE costs a few hundred tokens while DETAILED returns the full grid, and that provenance is attached — but it says nothing about rate limits, freshness/caching, or how large the DETAILED payload can get.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The substance is front-loaded correctly — definition first, then output modes, then provenance — but roughly a third of the text is legal boilerplate ('For educational purposes only. Not trading advice. Not investment advice...') that repeats the same idea three times and crowds out operational detail.

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?

For a read-only, three-parameter tool the essentials are present, but with no output schema the description carries the return-value burden and only describes the payload in prose ('densest levels and coverage', 'full grid', 'share of open interest') without any indication of fields or grouping. It is adequate but leaves the agent guessing at the response shape.

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 67%: coin and timeframe already carry enum descriptions in the schema, while response_format has no schema description. The description fills exactly that gap by defining the two modes and their output volume, which is the one piece of semantics the schema omits.

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?

Names the resource precisely (observed liquidation price levels bucketed by price, with realized liquidations overlaid and OI share) and scopes it to four coins. It's clear enough to pick apart from generic market tools, but it never differentiates itself from the very similar sibling tape_liquidations, leaving the agent to guess which liquidation view to call.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many tape_* siblings. The only selection help is the CONCISE vs DETAILED format tradeoff, which guides parameter choice inside this tool rather than tool selection.

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.

Resources