Skip to main content
Glama

get_hip4_summary

Read-onlyIdempotent

Get a HIP-4 24-hour market summary for a coin, returning price, volume, open interest, and implied probability.

Instructions

Get a combined HIP-4 24h market summary for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns price, volume, and OI aggregates. mark_price is an implied probability (0..1), not USD.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResult data object

Implementation Reference

  • src/index.ts:1743-1753 (registration)
    Registration of the get_hip4_summary tool using registerTool helper. Describes the tool as returning a combined HIP-4 24h market summary with price, volume, and OI aggregates. Accepts a coin parameter (Hip4CoinParam) and has ObjectOutputSchema.
    // HIP-4 Summary
    registerTool(
      "get_hip4_summary",
      "Get a combined HIP-4 24h market summary for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns price, volume, and OI aggregates. mark_price is an implied probability (0..1), not USD.",
      { coin: Hip4CoinParam },
      ObjectOutputSchema,
      async (params) => {
        const result = await hip4Request(`/summary/${normalizeHip4Coin(params.coin)}`);
        return formatResponse(result.data);
      }
    );
  • Handler function for get_hip4_summary. Makes a GET request to /v1/hyperliquid/hip4/summary/{coin} via the hip4Request helper and returns the formatted response.
    async (params) => {
      const result = await hip4Request(`/summary/${normalizeHip4Coin(params.coin)}`);
      return formatResponse(result.data);
    }
  • The hip4Request helper function shared by all HIP-4 tools, including get_hip4_summary. Handles constructing the URL with query params, setting auth headers, making the fetch call, and parsing the response.
    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 used to normalize HIP-4 coin symbols (bare numeric, or legacy #0 / %230 forms) before making the API request.
    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);
    }
  • The Hip4CoinParam Zod schema used for input validation of the coin parameter in get_hip4_summary.
    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."
      );
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 behavioral details: returns price, volume, OI aggregates, and clarifies mark_price is implied probability (0..1) not USD, which is important for correct interpretation. No contradiction with 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 front-load purpose and coin example, then clarify return fields and mark_price semantics. Every sentence adds value with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so description need not detail return structure. It adequately names the key aggregates (price, volume, OI) and resolves ambiguity about mark_price. For a summary tool with good annotations, this is complete.

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% with a detailed description of the coin parameter. Description echoes the accepted forms but mainly adds context about the summary itself. With high schema coverage, baseline is 3; description adds some value but is largely redundant on parameter meaning.

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 the tool retrieves a combined HIP-4 24h market summary for a coin, with specific verb 'Get', resource 'HIP-4 summary', and scope '24h'. It distinguishes from sibling summary tools like get_hip3_summary by explicitly naming HIP-4.

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?

Description provides guidance on coin format (canonical vs legacy forms) and references get_hip4_instruments for listing coins. While it does not explicitly enumerate when to use vs alternatives, the context is clear for a high-level summary tool among many HIP-4 detail 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