Skip to main content
Glama

get_order_history

Read-onlyIdempotent

Retrieve Hyperliquid order history with user addresses. Filter by coin, status, type, time range, and wallet to track order lifecycle events.

Instructions

Get Hyperliquid order history with user attribution (Build+ tier). Returns order lifecycle events including placements, fills, cancellations, and modifications with user addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCoin/market symbol, e.g. 'BTC', 'ETH', 'SOL'
startNoStart timestamp (Unix ms or ISO). Defaults to 24h ago.
endNoEnd timestamp (Unix ms or ISO). Defaults to now.
limitNoMax records to return (default 100, max 1000)
cursorNoPagination cursor from previous response's nextCursor
userNoUser wallet address filter (e.g., '0x1234...')
statusNoFilter orders by status
order_typeNoFilter orders by type

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordsYesArray of result records
countYesTotal number of records in the full result set
nextCursorNoCursor for next page, if more results available

Implementation Reference

  • src/index.ts:1011-1024 (registration)
    Registration of the 'get_order_history' tool using registerHistoryTool. It delegates to api().hyperliquid.orders.history() with CoinParam (normalized via normalizeHLCoin), plus optional user, status, and order_type filters.
    // Hyperliquid Order History
    registerHistoryTool(
      "get_order_history",
      "Get Hyperliquid order history with user attribution (Build+ tier). Returns order lifecycle events including placements, fills, cancellations, and modifications with user addresses.",
      (coin, params) =>
        api().hyperliquid.orders.history(coin, params as any),
      CoinParam,
      normalizeHLCoin,
      {
        user: UserParam,
        status: OrderStatusParam,
        order_type: OrderTypeParam,
      }
    );
  • Input parameter schemas used by get_order_history: UserParam (optional wallet address), OrderStatusParam (open/filled/cancelled/expired), OrderTypeParam (limit/market/trigger/tpsl), and the TriggeredParam boolean filter.
    const UserParam = z
      .string()
      .optional()
      .describe("User wallet address filter (e.g., '0x1234...')");
    
    const OrderStatusParam = z
      .enum(["open", "filled", "cancelled", "expired"])
      .optional()
      .describe("Filter orders by status");
    
    const OrderTypeParam = z
      .enum(["limit", "market", "trigger", "tpsl"])
      .optional()
      .describe("Filter orders by type");
    
    const TriggeredParam = z
      .boolean()
      .optional()
      .describe("Filter TP/SL orders by triggered status");
  • registerHistoryTool — the registration helper that builds the handler for history-based tools. It resolves time range, limit, cursor, passes extra params (like user/status/order_type) and calls the SDK, then formats via formatCursorResponse.
    // Pattern 4: History with cursor pagination (coin + time range)
    function registerHistoryTool(
      name: string,
      description: string,
      sdkCall: (coin: string, params: Record<string, unknown>) => Promise<{ data: unknown; nextCursor?: string }>,
      coinSchema: z.ZodString,
      normFn: (coin: string) => string,
      extraSchema?: ZodRawShape
    ): void {
      const schema: ZodRawShape = { coin: coinSchema, ...HistoryParams };
      if (extraSchema) Object.assign(schema, extraSchema);
    
      registerTool(name, description, schema, ListOutputSchema, async (params) => {
        const { coin, start, end, limit, cursor, ...extra } = params;
    
        const timeRange = resolveTimeRange(start, end);
        const sdkParams: Record<string, unknown> = {
          ...timeRange,
          limit: resolveLimit(limit),
        };
    
        if (cursor) sdkParams.cursor = cursor;
    
        // Pass through extra params (interval, side, etc.)
        for (const [k, v] of Object.entries(extra)) {
          if (v !== undefined) sdkParams[k] = v;
        }
    
        const result = await sdkCall(normFn(coin), sdkParams);
        return formatCursorResponse(result);
      });
    }
  • The HistoryParams shared schema object (start, end, limit, cursor) that gets spread into get_order_history's input schema.
    const TimestampParam = z
      .union([z.number(), z.string()])
      .optional()
      .describe("Timestamp as Unix milliseconds or ISO 8601 string");
    
    const LimitParam = z
      .number()
      .optional()
      .describe("Max records to return (default 100, max 1000)");
    
    const CursorParam = z
  • formatCursorResponse helper used to format paginated results with nextCursor support.
    function formatCursorResponse(result: {
      data: unknown;
      nextCursor?: string;
    }): McpContent {
      return formatResponse(result.data, {
        nextCursor: result.nextCursor,
        paginated: true,
      });
    }
Behavior4/5

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

Annotations already indicate read-only, idempotent, open world. Description adds that it returns order lifecycle events with user addresses, providing useful behavioral context beyond annotations.

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?

Two sentences: first states purpose and tier, second describes output. Efficient and front-loaded with key information.

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?

Description covers purpose, tier, and output content. Output schema exists, so return details are handled. Lacks explanation of pagination or filtering options, but these are in schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameter descriptions, so baseline is 3. Description adds overall context about what the data represents (lifecycle events, attribution), which aids parameter understanding.

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

Purpose5/5

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

Description clearly states 'Get Hyperliquid order history with user attribution (Build+ tier)' and lists specific lifecycle events, distinguishing from sibling tools by specifying tier and user attribution.

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?

Description mentions 'Build+ tier' implying restricted use, but does not explicitly state when to use or alternatives. No guidance on when not to use.

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/0xArchiveIO/0xarchive-mcp'

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