Skip to main content
Glama

get_hip4_instrument

Read-onlyIdempotent

Retrieve detailed metadata for a specific HIP-4 instrument using its coin symbol, including outcome ID, side, asset details, and settlement status.

Instructions

Get details for a single HIP-4 instrument by coin symbol (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns per-side metadata including outcome_id, side, asset_id, name, recurring class/underlying/expiry, builder address, and is_settled status.

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:1574-1583 (registration)
    Registration of the 'get_hip4_instrument' tool via registerTool(). It accepts a 'coin' parameter (validated by Hip4CoinParam), calls the HIP-4 REST API endpoint /instruments/:coin, and returns the result.
    registerTool(
      "get_hip4_instrument",
      "Get details for a single HIP-4 instrument by coin symbol (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns per-side metadata including outcome_id, side, asset_id, name, recurring class/underlying/expiry, builder address, and is_settled status.",
      { coin: Hip4CoinParam },
      ObjectOutputSchema,
      async (params) => {
        const result = await hip4Request(`/instruments/${normalizeHip4Coin(params.coin)}`);
        return formatResponse(result.data);
      }
    );
  • Handler function for get_hip4_instrument. Normalizes the coin symbol using normalizeHip4Coin, makes a GET request to /v1/hyperliquid/hip4/instruments/{coin} via hip4Request, and formats the response.
      async (params) => {
        const result = await hip4Request(`/instruments/${normalizeHip4Coin(params.coin)}`);
        return formatResponse(result.data);
      }
    );
  • Input schema (Zod) for the HIP-4 coin parameter used by get_hip4_instrument and other HIP-4 tools. Validates it's a string.
    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."
      );
  • Normalization helper for HIP-4 coin symbols. Strips legacy # or %23 prefixes, leaving bare numeric form. Used by get_hip4_instrument's handler before making the API call.
    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);
    }
  • Helper function that makes all HIP-4 REST API calls (including the one for get_hip4_instrument). Constructs the URL with query params, adds auth headers, handles errors, and returns parsed data with optional cursor.
    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 declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds value by listing the return fields (outcome_id, side, asset_id, etc.), offering transparency beyond safety guarantees.

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 with example, second details accepted forms and return fields. No wasted words, front-loaded.

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?

Given the tool's simplicity, existence of output schema, and thorough schema parameter description, the tool description is complete. It covers identification, variations, and usage hint.

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?

Input schema covers 100% of parameter description with detailed explanation of coin forms. Tool description restates this with an example, adding minimal extra value. Baseline 3 applies.

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?

Clearly states 'Get details for a single HIP-4 instrument by coin symbol', specifying the verb, resource, and parameter. Distinguishes from sibling tools like get_hip4_instruments (list all) and other get_hip4_* tools.

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

Usage Guidelines5/5

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

Explicitly mentions when to use this tool (single instrument) and directs to get_hip4_instruments for listing all. Also clarifies accepted coin forms, providing concrete guidance.

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