Skip to main content
Glama

Hl wallet positions

hl_wallet_positions
Read-onlyIdempotent

Live Hyperliquid trader & whale wallet inspector: account equity, margin usage %, withdrawable USDC, net delta, and open perp positions with entry, leverage, liquidation distance %, and unrealized PnL. $0.003 per call over x402 or X-API-Key. Not advice.

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": {
      "address": "<address>"
    },
    "name": "hl_wallet_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesHyperliquid 0x EVM wallet or vault address.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: a fixed $0.003 per-call cost and the two accepted auth paths (x402 payment payload or X-API-Key). It does not cover failure behavior for non-Hyperliquid or empty wallets, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first front-loads the capability and the returned fields, the second carries cost and auth. Nothing is redundant with the title, and no filler separates the key facts.

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, so the description must carry return semantics, and it does via the field enumeration. Both parameters are documented, cost and auth are stated, and annotations cover safety; only edge-case behavior (invalid address, empty positions) is unaddressed, which is a minor gap for a read-only inspector.

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

Parameters4/5

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

With 100% schema description coverage, the schema already explains both 'address' (Hyperliquid 0x EVM wallet or vault) and 'payment' (signed x402 payload). The description reinforces the domain ('trader & whale wallet') and the payment mechanism, which meaningfully ties the 'payment' parameter to the x402 flow rather than merely restating the schema, so it edges above the baseline 3.

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 names a specific verb and resource ('Live Hyperliquid trader & whale wallet inspector') and enumerates exactly what is returned: equity, margin usage %, withdrawable USDC, net delta, and perp positions with entry, leverage, liquidation distance, and unrealized PnL. That specificity distinguishes it from generic wallet siblings such as arc_wallet or evm_wallet_balance, which would not be expected to return perp position detail.

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?

Usage is only implied: an agent can infer this tool is for inspecting a Hyperliquid perp wallet, but the description never states when to choose it over arc_wallet, wallet_profile, or evm_wallet_balance, nor any exclusions. No prerequisites or conditions are given beyond the implicit Hyperliquid scope.

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