Skip to main content
Glama

waiaas_hl_get_trade_history

Retrieve Hyperliquid trade history and fill data for a specified wallet to analyze transaction patterns and track trading activity.

Instructions

Get Hyperliquid trade history (fills) for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID.
limitNoMaximum number of fills to return.

Implementation Reference

  • The tool 'waiaas_hl_get_trade_history' is registered here. The handler function performs an API request to the backend '/v1/wallets/${walletId}/hyperliquid/fills' to fetch trade history and returns the formatted result.
    // hl_get_trade_history
    server.tool(
      'waiaas_hl_get_trade_history',
      withWalletPrefix('Get Hyperliquid trade history (fills) for a wallet.', walletContext?.walletName),
      {
        wallet_id: z.string().optional().describe('Wallet ID.'),
        limit: z.string().optional().describe('Maximum number of fills to return.'),
      },
      async (args) => {
        const params = new URLSearchParams();
        if (args.limit) params.set('limit', args.limit);
        const walletId = args.wallet_id || 'default';
        const qs = params.toString();
        const result = await apiClient.get(`/v1/wallets/${walletId}/hyperliquid/fills${qs ? '?' + qs : ''}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only hints at behavior by specifying 'fills' (executed trades) but fails to mention read-only safety, pagination behavior (despite the limit parameter being a string), authentication requirements, or return format.

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, front-loaded with the action and resource, zero waste. Every word earns its place by conveying the specific domain (Hyperliquid), operation (Get), and target (wallet/fills).

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?

Adequate for a simple 2-parameter tool with full schema coverage, but minimal given the lack of annotations and output schema. It sufficiently identifies the operation but omits behavioral context that would help an agent understand result sets or pagination.

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 description coverage is 100%, establishing a baseline of 3. The description mentions 'wallet' (aligning with wallet_id) and 'fills' (aligning with limit description), but adds no additional semantics regarding the string type of limit or format requirements for wallet_id.

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 clearly states the specific verb (Get), resource (Hyperliquid trade history), and scope (fills for a wallet). The '(fills)' clarifies this returns executed trades, distinguishing it from sibling tools like get_open_orders or get_positions, though it doesn't explicitly name those alternatives.

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?

No explicit guidance on when to use versus alternatives (e.g., get_open_orders for pending trades), no prerequisites mentioned, and no exclusions provided. Users must infer suitability from the name and brief description.

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