Skip to main content
Glama
Sign In
traivo-mcp

traivo-mcp

Official
by traivoxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Hyperliquid account

get_hyperliquid_account
Read-onlyIdempotent

Retrieve a read-only Hyperliquid account summary by wallet address, including account value, margin, positions, PnL, liquidation distance, and spot balances using public data; no keys required.

Instructions

Read-only summary of a Hyperliquid account by address: account value, withdrawable, margin used, total notional, open perp positions (side, size, entry, mark, PnL, ROE, liquidation price and distance %, leverage) and spot balances. Public data; no keys.

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

Input Schema

NameRequiredDescriptionDefault
addressYesEVM wallet address (0x…). Public data only; no signature needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context, which it does: 'Public data; no keys' preempts any auth/key concern, and the perp/spot breakdown signals what data surfaces exist. It does not state behavior for unknown/empty addresses or whether unfunded addresses error versus return zeros.

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?

One dense sentence, front-loaded with the read-only framing and scoped 'by address' before the field inventory, with zero filler. The long parenthetical field list is slightly list-heavy but every item is informative, so it earns its place.

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?

With no output schema, the description must describe return values, and it does so explicitly across perp positions and spot balances, including derived metrics like ROE and liquidation distance. Remaining gaps are minor: units/number formatting and empty-account behavior are unaddressed.

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 a single parameter with 100% schema description coverage, including a regex pattern and the note that no signature is needed, so the schema carries the semantics. The description only echoes 'by address' and adds nothing about chain, address normalization, or case sensitivity — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read-only summary of a Hyperliquid account by address', followed by an explicit inventory of what is returned (account value, withdrawable, margin used, perp positions, spot balances). The purpose is unambiguous, but it never contrasts itself with the overlapping sibling get_portfolio, so sibling differentiation is left to inference.

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 is the tool for inspecting a single Hyperliquid account's positions and balances. There is no explicit when-to-use statement, no guidance on when get_portfolio or get_scorecard would be the better choice, and no preconditions beyond the address format.

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

Deploy Server

Other Tools