Skip to main content
Glama

AINDEX

What Hyperliquid's best traders hold

hyperliquid_whales
Read-only

The open positions in a coin or stock perp of Hyperliquid's 40 most profitable accounts this month that still hold $100k or more: longs against shorts by count and size, and the largest positions with entry, leverage, PnL and liquidation price.

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": {
      "coin": "<coin>"
    },
    "name": "hyperliquid_whales"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the load and does it well: it defines the cohort (40 most profitable this month, $100k+ still held), the aggregation performed, and the fields surfaced (entry, leverage, PnL, liquidation price). It adds no caveats about refresh cadence or whether the cohort resets monthly, which keeps it from 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?

One sentence, front-loaded with the resource, then the breakdown of returned fields. Every clause carries information — the cohort filter, the count/size split, the per-position fields. The nested qualifier 'this month that still hold $100k or more' is slightly dense but necessary.

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 must convey return content, and it does: aggregate long/short counts and sizes plus a list of largest positions with their fields. For a one-parameter read-only tool this is close to complete; only symbol format and any result-size limits are unstated.

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 0% for the single required 'coin' parameter, so the description must compensate. Saying 'a coin or stock perp' usefully signals that equity perps are valid inputs (consistent with the pattern allowing ':' and '/'), but it gives no format example or case convention, leaving the agent to guess at the exact symbol syntax.

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 — aggregated open positions of Hyperliquid's 40 most profitable accounts this month, with longs vs shorts by count and size plus the largest positions. That is far more concrete than the name alone. It does not, however, distinguish itself from plausible siblings such as hyperliquid_outcomes, so it stops short of a 5.

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 guidance, no statement of when this is the wrong tool, and no named alternative. The agent must infer from the cohort description (profitable whales) that this is for sentiment/positioning analysis rather than, say, general market data.

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