whale-data

Hyperliquid wallet book

hl_wallet

Read-onlyIdempotent

One Hyperliquid account: live positions, equity, leverage, net bias and unrealized PnL, plus its recent whale-sized fills. The live book is public on Hyperliquid so it stays on the free plans; computed history (win rates, cadence, realized PnL) and the full fill trail need a paid plan. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max recent fills returned for this account. Defaults to 50, hard ceiling 200 for everyone and no plan raises it. The free plans receive 3 of them whatever is asked for, and the live positions come back either way.
`address`	Yes	Hyperliquid account address, 0x followed by 40 hex characters. Required. Every hl_whales row carries the wallet that filled it, so it can be passed straight in. An address outside the tracked set answers tracked:false, which is a coverage fact and not an account holding nothing.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`error`	No	invalid_address when the address is not 0x plus 40 hex characters. Nothing was looked up.
`capped`	No	Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
`prints`	No	Recent whale-sized fills for this account. Keyless connections receive 3 of them whatever was asked for.
`address`	No	The account address, normalised.
`profile`	No	The live account: what it holds, equity, dollars open, leverage, which way it leans and unrealized profit. Public on Hyperliquid, so it stays keyless.
`tracked`	No	False when this account is outside the tracked set. A coverage fact, not an account holding nothing.
`access_note`	No	What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
`locked_layers`	No	Keyless only: which computed blocks a paid plan adds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / limit / description

Previous value: -"Max recent fills returned for this account. Defaults to 50, hard ceiling 200 for everyone and no plan raises it. Keyless calls receive 3 of them whatever is asked for, and the live positions come back either way."New value: +"Max recent fills returned for this account. Defaults to 50, hard ceiling 200 for everyone and no plan raises it. The free plans receive 3 of them whatever is asked for, and the live positions come back either way."

Changed1 schema field changedSep 2, 2026

changedOutput schema / properties / locked_layers / description

Previous value: -"Keyless only: which computed blocks a developer plan adds."New value: +"Keyless only: which computed blocks a paid plan adds."

Changed3 schema fields changedAug 13, 2026

addedInput schema / properties / address / description

Added value: +"Hyperliquid account address, 0x followed by 40 hex characters. Required. Every hl_whales row carries the wallet that filled it, so it can be passed straight in. An address outside the tracked set answers tracked:false, which is a coverage fact and not an account holding nothing."

addedInput schema / properties / limit / description

Added value: +"Max recent fills returned for this account. Defaults to 50, hard ceiling 200 for everyone and no plan raises it. Keyless calls receive 3 of them whatever is asked for, and the live positions come back either way."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "access_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
+    },
+    "address": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The account address, normalised."
+    },
+    "capped": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "applied": {
+              "description": "The value actually used.",
+              "type": "number"
+            },
+            "argument": {
+              "description": "Which argument was cut down, for example limit or hours.",
+              "type": "string"
+            },
+            "by": {
+              "description": "Why it was cut: keyless for the free ceiling, plan_max for a paid ceiling, tool_max for a ceiling no plan raises.",
+              "type": "string"
+            },
+            "max": {
+              "description": "The ceiling that applied.",
+              "type": "number"
+            },
+            "requested": {
+              "description": "The value the caller asked for.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "argument",
+            "requested",
+            "applied",
+            "max",
+            "by"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit."
+    },
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "invalid_address when the address is not 0x plus 40 hex characters. Nothing was looked up."
+    },
+    "locked_layers": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Keyless only: which computed blocks a developer plan adds."
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading."
+    },
+    "prints": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Recent whale-sized fills for this account. Keyless connections receive 3 of them whatever was asked for."
+    },
+    "profile": {
+      "description": "The live account: what it holds, equity, dollars open, leverage, which way it leans and unrealized profit. Public on Hyperliquid, so it stays keyless."
+    },
+    "tracked": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this account is outside the tracked set. A coverage fact, not an account holding nothing."
+    }
+  },
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses meaningful behavior: the live book is public and available on free plans, while win rates, cadence, realized PnL, and the full fill trail are plan-gated. The closing 'Descriptive market data only' also sets expectations about scope. This adds real value beyond the annotations and does not contradict them.

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?

The description is compact and front-loaded: the first sentence states what the tool returns, and the second adds the plan nuance. Every sentence earns its place, though the final 'Descriptive market data only' clause is somewhat generic and could be trimmed or folded in without losing much.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return-value documentation is already handled. The description covers scope, plan gating, and public-data availability, while the schema covers address and limit semantics. A qualified agent has everything needed to invoke it correctly.

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?

Both parameters are fully documented in the input schema, including the address format, the tracked/untracked account distinction, and the limit behavior with defaults, free-plan caps, and ceilings. The description itself adds little parameter-level detail, so the schema carries the semantic weight, which is the expected baseline.

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 'One Hyperliquid account' and enumerates the exact contents: live positions, equity, leverage, net bias, unrealized PnL, and recent whale-sized fills. This makes the resource and scope unmistakable, even without an explicit verb, and clearly distinguishes it from aggregate siblings like hl_whales or hl_traders.

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

Usage Guidelines4/5

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

The description communicates a clear use case: retrieve a single Hyperliquid account's live book and recent fills. It also gives plan-based guidance by saying the live public book stays on free plans, while computed history and the full fill trail require a paid plan. It does not name an alternative sibling for paid-only data, so it stops short of full exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All whale-data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?