Skip to main content
Glama

waiaas_hl_get_open_orders

Retrieve active trading orders from Hyperliquid for a specific wallet and sub-account to monitor positions and manage trades.

Instructions

Get Hyperliquid open orders for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID.
sub_accountNoSub-account address (hex).

Implementation Reference

  • The handler implementation for the MCP tool 'waiaas_hl_get_open_orders' which queries the /v1/wallets/{walletId}/hyperliquid/orders endpoint.
    // hl_get_open_orders
    server.tool(
      'waiaas_hl_get_open_orders',
      withWalletPrefix('Get Hyperliquid open orders for a wallet.', walletContext?.walletName),
      {
        wallet_id: z.string().optional().describe('Wallet ID.'),
        sub_account: z.string().optional().describe('Sub-account address (hex).'),
      },
      async (args) => {
        const params = new URLSearchParams();
        if (args.sub_account) params.set('subAccount', args.sub_account);
        const walletId = args.wallet_id || 'default';
        const qs = params.toString();
        const result = await apiClient.get(`/v1/wallets/${walletId}/hyperliquid/orders${qs ? '?' + qs : ''}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. States 'Get' implying read-only, but provides no information on rate limits, caching, authentication requirements, or return structure. Silent on behavior when optional parameters are omitted.

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?

Single sentence, six words. Information is front-loaded with the verb and domain. No redundancy or wasted text, though brevity contributes to other dimension weaknesses.

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?

Minimally adequate for a simple read tool with two optional string parameters and no output schema. Fails to explain the relationship between wallet_id and sub_account (mutually exclusive, hierarchical?) or what constitutes an 'open order' in this context.

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?

Schema coverage is 100% with documented 'wallet_id' and 'sub_account' parameters. Description adds no semantic detail beyond implying wallet_id represents the wallet. Baseline score applies as schema does the heavy lifting.

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?

Clearly identifies the operation (Get), platform (Hyperliquid), and resource (open orders), distinguishing it from sibling tools like waiaas_hl_get_positions (positions) and waiaas_pm_get_orders (Polymarket). Lacks precision only in defining 'open orders' (active unfilled vs executed).

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?

Provides no explicit guidance on when to use this tool versus alternatives like waiaas_hl_get_trade_history (filled orders) or waiaas_pm_get_orders. The Hyperliquid prefix assists navigation but no usage conditions are stated.

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