Skip to main content
Glama

get_hip4_trades

Read-onlyIdempotent

Retrieve HIP-4 trade history for a coin, including price, size, side, and timestamps. Supports time range filtering and cursor pagination.

Instructions

Get HIP-4 trade/fill history for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns price, size, side, and timestamps over a time range. Supports cursor pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesHIP-4 outcome-market coin symbol. Canonical form is the bare numeric '<10*outcome_id + side>' (e.g. '0' for outcome 0 Yes, '1' for outcome 0 No, '10' for outcome 1 Yes). The legacy '#0' and '%230' forms are also accepted. Use get_hip4_instruments to list all.
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

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:1659-1673 (registration)
    Tool 'get_hip4_trades' registration using registerTool. Defines input schema (coin with Hip4CoinParam + HistoryParams), output schema (ListOutputSchema), and the handler that calls hip4Request to GET /trades/{coin} with query params.
    // HIP-4 Trades
    registerTool(
      "get_hip4_trades",
      "Get HIP-4 trade/fill history for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns price, size, side, and timestamps over a time range. Supports cursor pagination.",
      {
        coin: Hip4CoinParam,
        ...HistoryParams,
      },
      ListOutputSchema,
      async (params) => {
        const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor);
        const result = await hip4Request(`/trades/${normalizeHip4Coin(params.coin)}`, q);
        return formatCursorResponse(result);
      }
    );
  • The handler function that executes the tool logic. It builds query params via buildHistoryQuery, normalizes the HIP-4 coin, calls hip4Request to GET /v1/hyperliquid/hip4/trades/{coin}, and returns formatted cursor response.
    async (params) => {
      const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor);
      const result = await hip4Request(`/trades/${normalizeHip4Coin(params.coin)}`, q);
      return formatCursorResponse(result);
    }
  • Hip4CoinParam - the Zod schema for the coin input parameter used by get_hip4_trades, describing HIP-4 outcome-market coin symbols in bare numeric form.
    const Hip4CoinParam = z
      .string()
      .describe(
        "HIP-4 outcome-market coin symbol. Canonical form is the bare numeric '<10*outcome_id + side>' (e.g. '0' for outcome 0 Yes, '1' for outcome 0 No, '10' for outcome 1 Yes). The legacy '#0' and '%230' forms are also accepted. Use get_hip4_instruments to list all."
      );
  • buildHistoryQuery - helper function used by get_hip4_trades handler to construct query parameters (start, end, limit, cursor) from the tool's input params.
    function buildHistoryQuery(
      start?: number | string,
      end?: number | string,
      limit?: number,
      cursor?: string,
      extra?: Record<string, unknown>
    ): Record<string, unknown> {
      const range = resolveTimeRange(start, end);
      const q: Record<string, unknown> = {
        start: range.start,
        end: range.end,
        limit: resolveLimit(limit),
      };
      if (cursor) q.cursor = cursor;
      if (extra) {
        for (const [k, v] of Object.entries(extra)) {
          if (v !== undefined) q[k] = v;
        }
      }
      return q;
    }
  • hip4Request - the HTTP helper that makes REST API calls to the HIP-4 endpoint (https://api.0xarchive.io/v1/hyperliquid/hip4). Used by get_hip4_trades handler to GET /trades/{coin}.
    async function hip4Request(
      path: string,
      query?: Record<string, unknown>
    ): Promise<{ data: unknown; nextCursor?: string }> {
      const url = new URL(`${HIP4_BASE_PATH}${path}`, HIP4_BASE_URL);
      if (query) {
        for (const [k, v] of Object.entries(query)) {
          if (v === undefined || v === null) continue;
          url.searchParams.set(k, String(v));
        }
      }
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "User-Agent": "0xarchive-mcp/1.9.0",
      };
      if (apiKey) headers["X-API-Key"] = apiKey;
    
      const controller = new AbortController();
      const timeout = setTimeout(() => controller.abort(), 60000);
      try {
        const response = await fetch(url.toString(), {
          method: "GET",
          headers,
          signal: controller.signal,
        });
        const text = await response.text();
        let body: any;
        try {
          body = text ? JSON.parse(text) : null;
        } catch {
          body = text;
        }
        if (!response.ok) {
          const requestId =
            response.headers.get("x-request-id") || body?.meta?.requestId;
          const message =
            (body && (body.error?.message || body.error || body.message)) ||
            `HTTP ${response.status}`;
          throw new OxArchiveError(message, response.status, requestId ?? undefined);
        }
        if (body && typeof body === "object" && "data" in body) {
          return {
            data: body.data,
            nextCursor: body.meta?.nextCursor,
          };
        }
        return { data: body };
      } finally {
        clearTimeout(timeout);
      }
    }
Behavior4/5

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

Annotations (readOnlyHint, idempotentHint) are consistent, and the description adds that it returns price, size, side, timestamps over a time range with cursor pagination. No contradictions and good additional 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?

The description is concise, using only two sentences to convey the core purpose, supported formats, and features like time range and pagination. No unnecessary 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?

Given the output schema exists, the description adequately covers the tool's function, coin format, time range, and pagination. It does not need to detail return values, but could mention error handling or rate limits.

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%, providing baseline 3. The description adds coin format details already present in the schema, offering no new parameter semantics beyond what the schema already provides.

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?

The description clearly states it retrieves HIP-4 trade/fill history for a coin, specifying the verb 'Get' and resource 'trade/fill history'. It also distinguishes coin format and mentions cursor pagination, differentiating it from siblings like get_hip4_trades_recent.

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?

The description does not explicitly state when to use this vs. siblings. While it mentions pagination and coin format, it lacks guidance on when to prefer this over get_hip4_trades_recent or other trade-related tools.

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