Skip to main content
Glama

get_hip4_order_history

Read-onlyIdempotent

Fetch HIP-4 order lifecycle events for a coin symbol, including placements, fills, cancellations, and modifications. Filter by user, status, order type, and time range.

Instructions

Get HIP-4 order lifecycle events with user attribution (Pro+ tier) for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns placements, fills, cancellations, modifications.

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
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

  • The async handler function that builds the history query, calls the HIP-4 REST API endpoint /orders/{coin}/history, and formats the cursor-paginated response.
      async (params) => {
        const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor, {
          user: params.user,
          status: params.status,
          order_type: params.order_type,
        });
        const result = await hip4Request(
          `/orders/${normalizeHip4Coin(params.coin)}/history`,
          q
        );
        return formatCursorResponse(result);
      }
    );
  • Input schema defining the coin (Hip4CoinParam), history params (start/end/limit/cursor), and optional filters (user, status, order_type). Output schema is ListOutputSchema.
    {
      coin: Hip4CoinParam,
      ...HistoryParams,
      user: UserParam,
      status: OrderStatusParam,
      order_type: OrderTypeParam,
    },
  • src/index.ts:1777-1801 (registration)
    Registration of the 'get_hip4_order_history' tool using the registerTool helper with name, description, input/output schemas, and handler.
    // HIP-4 Order History
    registerTool(
      "get_hip4_order_history",
      "Get HIP-4 order lifecycle events with user attribution (Pro+ tier) for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns placements, fills, cancellations, modifications.",
      {
        coin: Hip4CoinParam,
        ...HistoryParams,
        user: UserParam,
        status: OrderStatusParam,
        order_type: OrderTypeParam,
      },
      ListOutputSchema,
      async (params) => {
        const q = buildHistoryQuery(params.start, params.end, params.limit, params.cursor, {
          user: params.user,
          status: params.status,
          order_type: params.order_type,
        });
        const result = await hip4Request(
          `/orders/${normalizeHip4Coin(params.coin)}/history`,
          q
        );
        return formatCursorResponse(result);
      }
    );
  • buildHistoryQuery helper that resolves time range, limit, cursor, and extra params for history endpoints.
    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 helper that makes authenticated GET requests to the HIP-4 REST API with timeout, error handling, and cursor extraction.
    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 already indicate read-only, idempotent, and open-world. The description adds value by detailing the return content (placements, fills, cancellations, modifications) and clarifying coin format acceptance. It also notes user attribution behavior and tier requirement, going beyond the structured 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 two sentences, directly stating the core functionality and coin format. Every word serves a purpose, with no fluff or repetition. It is front-loaded with the key action.

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 tool has 8 parameters and an output schema, the description covers the essential purpose and return types. It explains the coin format and tier requirement. However, it lacks details about pagination or how the user field relates to attribution, leaving minor gaps for an agent.

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%, so parameters are well-documented. The description's mention of coin forms and event types adds some context but largely overlaps with parameter descriptions. No new parameter semantics are introduced beyond what the schema provides, resulting in a baseline score.

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 tool retrieves HIP-4 order lifecycle events with user attribution for a specific coin, listing the event types. However, it does not explicitly differentiate from siblings like get_order_history or get_hip3_order_history, leaving the agent to infer the HIP-4 specificity and Pro+ tier requirement.

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 this tool versus alternatives such as get_order_history or get_hip3_order_history. The description mentions 'Pro+ tier' which implies a usage constraint but does not help an agent choose between similar 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