Skip to main content
Glama

A Hyperliquid account by address: account value, margin

perps_account
Read-only

A Hyperliquid account by address: account value, margin used and withdrawable amount in USD, and each open position with side, size, entry and mark price, unrealised PnL, leverage and liquidation price. Read-only. Information only, not financial advice. Related tools on this server, for a different need: perps_markets when you need to list Hyperliquid perpetuals with funding and open interest. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "perps_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesHyperliquid account address, 0x…

Output Schema

NameRequiredDescriptionDefault
sourceNo
addressNo
checkedAtNo
positionsNo
disclaimerNo
marginUsedUsdNo
accountValueUsdNo
withdrawableUsdNo

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 state readOnlyHint and openWorldHint, and the description adds material behavior: $0.002 per successful call, payment via x402, and failed calls not charged. It also reiterates read-only and adds a not-financial-advice disclaimer, though it does not address data freshness or rate limits.

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 purpose and scope are front-loaded, and the pricing and alternative-tool sentences are useful. The first sentence is dense and some return-field detail duplicates the output schema, but nothing is seriously wasteful.

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 is simple, has an output schema for return values, and the description still supplies the key call context: resource scope, read-only nature, payment terms, and the sibling alternative. An agent has enough information to select and 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?

There is one required address parameter with 100% schema description coverage, and the description only echoes 'by address' without adding format, validation, or address-type semantics. With the schema carrying the parameter documentation, this is the baseline case.

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 definition names a specific resource ('A Hyperliquid account by address') and enumerates the account and position fields returned, so an agent can distinguish it from perps_markets. It is a clear resource-level statement, not a tautology.

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?

It explicitly points to perps_markets when the need is listing Hyperliquid perpetuals with funding and open interest, establishing the main sibling boundary. It does not spell out a negative condition or exclusion, so it falls short of a full when/when-not guideline.

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