Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

waiaas_hl_get_spot_balances

Retrieve Hyperliquid spot token balances for a wallet to monitor cryptocurrency holdings and manage portfolio allocation.

Instructions

Get Hyperliquid spot token balances for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID. Auto-resolved for single-wallet sessions.

Implementation Reference

  • packages/mcp/src/tools/hyperliquid.ts:118-129 (handler)
    The handler implementation for the 'waiaas_hl_get_spot_balances' tool, which fetches spot token balances from a Hyperliquid wallet.
    server.tool(
  'waiaas_hl_get_spot_balances',
  withWalletPrefix('Get Hyperliquid spot token balances for a wallet.', walletContext?.walletName),
  {
    wallet_id: z.string().optional().describe('Wallet ID. Auto-resolved for single-wallet sessions.'),
  },
  async (args) => {
    const walletId = args.wallet_id || 'default';
    const result = await apiClient.get(`/v1/wallets/${walletId}/hyperliquid/spot/balances`);
    return toToolResult(result);
  },
);

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden. It only implies a read-only operation via the word 'Get' but fails to describe the return format, error conditions, whether zero-balance tokens are included, or any Hyperliquid-specific behavioral nuances.

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 description is a single, front-loaded sentence with no extraneous words. However, given the absence of annotations and output schemas, its extreme brevity leaves informational gaps that slightly reduce its structural effectiveness.

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 with full schema coverage, the description is minimally adequate. However, it lacks completeness regarding output interpretation and tool selection rationale given the rich sibling ecosystem of balance and Hyperliquid-related tools.

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?

The input schema has 100% description coverage for the single 'wallet_id' parameter, including the auto-resolution note. The main description adds no semantic information about parameters, earning the baseline score for high schema coverage.

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 the specific verb 'Get' with the clear resource 'Hyperliquid spot token balances,' accurately describing the operation. While it implicitly distinguishes from siblings like 'get_balance' (general) and 'waiaas_hl_get_positions' (derivatives) via the 'Hyperliquid spot' qualifier, it does not explicitly differentiate from related balance-fetching tools.

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 invoke this tool versus alternatives like 'get_balance' or 'waiaas_hl_get_account_state'. It omits conditions, prerequisites, or scenarios where this specific endpoint should be preferred.

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