Skip to main content
Glama

Tape — Hyperliquid Analytics

Hyperliquid Whale Prints

tape_whale_prints
Read-onlyIdempotent

Recent fills of $100k or more from the top Hyperliquid wallets over the last 36 hours, with net buy/sell flow and the markets receiving the most of it. Filter by coins or minNotional, cap with limit (default 20, max 200). 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": {
      "coins": [
        "BTC"
      ],
      "limit": 20,
      "minNotional": 100000
    },
    "name": "tape_whale_prints"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinsNoRestrict to symbols.
limitNo
minNotionalNoOnly fills at or above this USD notional (the feed floor is 100000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "coins": [
      +      "BTC"
      +    ],
      +    "limit": 20,
      +    "minNotional": 100000
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description's job is to add operational context — and it does: a fixed 36-hour lookback, a $100k feed floor, and a default of 20 with a hard cap of 200. It stops short of stating refresh cadence, pagination, or what 'provenance' concretely contains.

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 substantive content is front-loaded in two efficient sentences, but the tail is five fragments of legal boilerplate ('For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated...') that consume a large share of the text without helping an agent call the tool.

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?

There is no output schema, and the description compensates by naming the returned payload — whale fills, net buy/sell flow, top markets, plus provenance. Combined with annotations covering the safety profile, the definition is sufficient to invoke correctly; only refresh/pagination details are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description closes the gap where it matters: it supplies the undocumented default for limit (20) and repeats the feed floor of 100000 so minNotional's lower bound is unambiguous relative to the data set. This is meaning beyond the raw schema types.

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?

The description opens with a specific resource and scope: '$100k or more' fills from 'top Hyperliquid wallets over the last 36 hours', plus net buy/sell flow and top receiving markets. That is concrete enough to separate it from siblings like tape_leaderboard or tape_liquidations without opening any schema.

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 says how to narrow results (coins, minNotional, limit) but never states when to reach for this tool versus a sibling feed such as tape_liquidations or tape_wallet_analysis. Usage is implied by the data window and threshold rather than explicitly guided.

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