Skip to main content
Glama

AINDEX

Where traders get liquidated

liquidation_map
Read-only

Hyperliquid's liquidation map for a coin or stock perp from real positions, not a model: AINDEX reads the open positions of Hyperliquid's largest accounts (exact liquidation prices) in a loop. Dollars liquidated within 1, 2, 5 and 10% of the mark on each side (longs below, shorts above), the five largest clusters and positions, and how much of Hyperliquid's open interest the scan covers.

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": "liquidation_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

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 already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context beyond that: the data comes from scanning the open positions of Hyperliquid's largest accounts 'in a loop', and the output reports how much of open interest the scan covers, which signals the result is a sample with a stated coverage bound. It does not discuss latency or refresh cadence for a loop-based scan, which would have pushed this to a 5.

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?

A single dense sentence, but it is front-loaded with the core value proposition ('liquidation map ... from real positions, not a model') and every subsequent clause adds substantive output detail. Slightly overpacked, yet nothing is filler.

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 and no annotation-level detail on returns, the description takes on that burden and does it well by specifying the exact buckets, side convention (longs below, shorts above), top-5 clusters, and sample coverage. The remaining gap is symbol format, which for a single required param matters but is a narrow miss.

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?

There is one required parameter (symbol) with 0% schema description coverage, so the description must carry format meaning. It only says 'for a coin or stock perp', giving the domain of the symbol but no examples or format guidance for the constrained pattern (colons, slashes, equals signs allowed), leaving the agent to guess how to encode a stock perp ticker.

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?

States a specific verb+resource: a liquidation map for a coin or stock perp built from real positions rather than a model, and it enumerates what the map contains (dollar buckets at 1/2/5/10% of mark, largest clusters, OI coverage). That is far more than a restatement of the name. It does not, however, explicitly differentiate itself from the sibling liquidation_risk, so the agent must infer the split.

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?

The phrase 'from real positions, not a model' implies this is the empirical option and hints at a modeled alternative, but no sibling is named and there is no explicit when-to-use / when-not-to-use statement. Usage is inferable from the described output rather than directed.

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