Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

waiaas_hl_get_account_state

Retrieve Hyperliquid account details including balances, margins, and positions to monitor trading status and manage risk.

Instructions

Get Hyperliquid account state (balances, margins, positions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID.

Implementation Reference

  • packages/mcp/src/tools/hyperliquid.ts:85-96 (handler)
    Tool registration and handler implementation for waiaas_hl_get_account_state, which fetches Hyperliquid account data via the apiClient.
    // hl_get_account_state
server.tool(
  'waiaas_hl_get_account_state',
  withWalletPrefix('Get Hyperliquid account state (balances, margins, positions).', walletContext?.walletName),
  {
    wallet_id: z.string().optional().describe('Wallet ID.'),
  },
  async (args) => {
    const walletId = args.wallet_id || 'default';
    const result = await apiClient.get(`/v1/wallets/${walletId}/hyperliquid/account`);
    return toToolResult(result);
  },

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. While 'Get' implies read-only, the description does not explicitly confirm this is non-destructive, nor does it mention real-time vs. cached data, rate limits, or authentication requirements specific to Hyperliquid.

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?

Extremely concise at 7 words. It is front-loaded with the action and resource, and the parenthetical list efficiently clarifies the return components without redundancy.

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

Completeness3/5

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

For a single-parameter read operation without output schema, the description adequately identifies the returned data components. However, it fails to address that the wallet_id parameter is optional (required: 0) or explain the Hyperliquid-specific context of 'account state'.

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?

With 100% schema description coverage (the 'wallet_id' parameter is fully documented in the schema as 'Wallet ID.'), the baseline score is 3. The description adds no additional parameter context (e.g., explaining that wallet_id is optional or what default applies when omitted).

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?

The description uses a specific verb ('Get') and resource ('Hyperliquid account state'), and the parenthetical '(balances, margins, positions)' defines the scope. However, it does not explicitly differentiate from sibling tools like 'waiaas_hl_get_positions' or 'waiaas_hl_get_spot_balances' which retrieve subsets of this data.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this aggregate tool versus the more specific sibling getters (e.g., waiaas_hl_get_positions). There are no conditions, prerequisites, or exclusion criteria mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server