Skip to main content
Glama

get_hip4_orderbook

Read-onlyIdempotent

Retrieve the current HIP-4 orderbook snapshot for an outcome-market coin. Returns bid and ask levels with implied probability prices.

Instructions

Get the current HIP-4 L2 orderbook snapshot for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns bids and asks. Note: mark_price for HIP-4 is an implied probability (0..1), not a USD price. Pro+ tier required.

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.
depthNoOrderbook depth — number of price levels per side

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResult data object

Implementation Reference

  • The handler function for the 'get_hip4_orderbook' tool. It accepts 'coin' and optional 'depth' parameters, normalizes the coin using normalizeHip4Coin, makes a request to /v1/hyperliquid/hip4/orderbook/{coin} via the hip4Request helper, and returns the response.
    registerTool(
      "get_hip4_orderbook",
      "Get the current HIP-4 L2 orderbook snapshot for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns bids and asks. Note: mark_price for HIP-4 is an implied probability (0..1), not a USD price. Pro+ tier required.",
      {
        coin: Hip4CoinParam,
        depth: DepthParam,
      },
      ObjectOutputSchema,
      async (params) => {
        const q: Record<string, unknown> = {};
        if (params.depth) q.depth = params.depth;
        const result = await hip4Request(`/orderbook/${normalizeHip4Coin(params.coin)}`, q);
        return formatResponse(result.data);
      }
    );
  • Input schema for get_hip4_orderbook: coin (Hip4CoinParam, a Zod string with HIP-4 outcome-market description) and optional depth (DepthParam, number). Output schema is ObjectOutputSchema (single data record).
    {
      coin: Hip4CoinParam,
      depth: DepthParam,
    },
    ObjectOutputSchema,
  • src/index.ts:1620-1635 (registration)
    Registration of the 'get_hip4_orderbook' tool via registerTool. Wired to the HIP-4 REST API endpoint /orderbook/{coin} rather than the SDK because the SDK's hip4 namespace was not yet available.
    // HIP-4 Orderbook (current)
    registerTool(
      "get_hip4_orderbook",
      "Get the current HIP-4 L2 orderbook snapshot for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns bids and asks. Note: mark_price for HIP-4 is an implied probability (0..1), not a USD price. Pro+ tier required.",
      {
        coin: Hip4CoinParam,
        depth: DepthParam,
      },
      ObjectOutputSchema,
      async (params) => {
        const q: Record<string, unknown> = {};
        if (params.depth) q.depth = params.depth;
        const result = await hip4Request(`/orderbook/${normalizeHip4Coin(params.coin)}`, q);
        return formatResponse(result.data);
      }
    );
  • The hip4Request helper function that performs the actual fetch to the HIP-4 REST API. Used by the orderbook handler to make the GET request.
    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);
      }
    }
  • The normalizeHip4Coin helper function that normalizes HIP-4 coin symbols (e.g., strips '#' or '%23' prefixes, falls back to URL-encoding). Used by the orderbook handler to normalize the coin parameter.
    function normalizeHip4Coin(coin: string): string {
      const trimmed = String(coin).trim();
      if (/^\d+$/.test(trimmed)) return trimmed;
      const stripped = trimmed.replace(/^(#|%23)/i, "");
      if (/^\d+$/.test(stripped)) return stripped;
      // Unknown shape — fall back to URL-encoding the original.
      return encodeURIComponent(trimmed);
    }
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds important behavioral context: mark_price is an implied probability (0..1) not USD, and Pro+ tier is required. This helps the agent understand special behavior.

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 three sentences, with the main purpose front-loaded. Every sentence provides essential information without redundancy or verbosity.

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?

The description covers coin format variations, mark_price interpretation, and tier requirement. It does not mention the depth parameter, but the output schema likely covers return structure. Overall sufficient for a simple snapshot tool.

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 baseline is 3. The description provides example coin formats and notes legacy forms, which reinforces the schema but adds minimal new semantic meaning for parameters.

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 the tool retrieves a HIP-4 L2 orderbook snapshot for a coin, with specific examples of coin formats and a note on mark_price interpretation. It semantically distinguishes from siblings like get_hip4_l4_orderbook (L4) and get_hip3_orderbook (HIP-3).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for current L2 orderbook data vs. historical (get_hip4_orderbook_history) and L4 (get_hip4_l4_orderbook), but does not explicitly state when to use this tool over siblings. It does mention a prerequisite (Pro+ tier).

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