Hyperliquid

Hyperliquid Spot Balances

hyperliquid_spot_balances

Read-onlyIdempotent

Spot token balances for one Hyperliquid wallet address -- per token: total, amount on hold in open orders, available (total minus hold) and entry notional in USDC. Includes the spot USDC balance. Public on-chain data, keyless. Use for "what tokens does this Hyperliquid wallet hold". e.g. {address:"0x31dea2516beee92135b96f464eeec3cf292a13f2"}.

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": {
      "limit": 5,
      "address": "0x31dea2516beee92135b96f464eeec3cf292a13f2"
    },
    "name": "hyperliquid_spot_balances"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max token rows to return, largest first (default 50). Totals always cover every token.
`address`	Yes	0x-prefixed 42-character wallet address.

Output Schema

Name	Required	Description	Default
`note`	No
`found`	No
`source`	No
`address`	No
`balances`	No
`returned`	No
`token_count`	No
`spot_usdc_total`	No
`total_entry_notional_usdc`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds useful context beyond that: the data is public on-chain and keyless, and the balance breakdown includes hold and available amounts plus entry notional in USDC.

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 key information is front-loaded in the first sentence and the usage cue follows naturally. It is compact overall, though the trailing example is somewhat redundant with the schema example.

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?

An output schema and rich annotations already cover the return shape and safety profile, so the description does not need to explain those. It provides enough context for a simple two-parameter read tool, though it could have clarified limit behavior more explicitly in prose.

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 100%, so both the address format and the limit behavior are already fully documented in the schema. The description adds a concrete example address but little else about parameter semantics, so the baseline of 3 applies.

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?

States a specific verb and resource: spot token balances for one Hyperliquid wallet address, and enumerates the per-token fields returned (total, hold, available, entry notional in USDC). This clearly differentiates it from siblings like hyperliquid_account_state and hyperliquid_spot_meta.

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?

Gives a concrete use case ("what tokens does this Hyperliquid wallet hold") and notes that it is public on-chain and keyless, which helps with when to use it. However, it does not explicitly name alternatives such as account_state or spot_meta or state when not to use this tool.

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

All Hyperliquid 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.