Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_official_oi

Retrieve official per-dex open interest from Hyperliquid's Info API. Get hourly snapshots with open interest, mark price, and 24h volume to cross-check computed OI with venue-reported ground truth.

Instructions

Official per-dex open interest for a coin, sourced from Hyperliquid's Info API (not derived from live_positions). Returns hourly snapshots with open interest, mark price, and 24h notional volume. Use when an agent needs venue-reported ground truth, per-dex breakdown, or wants to cross-check computed OI against official numbers. Default 7 days, max 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
coinYesCoin symbol (e.g. BTC, ETH, SOL). Use the bare ticker — dex is supplied via the 'dex' parameter, not prefix.
hoursNoNumber of hours of history (default 168 = 7 days, max 720 = 30 days)
dexNoWhich dex's official OI to return. Defaults to 'hl' (native Hyperliquid).hl

Implementation Reference

  • src/index.ts:1029-1045 (registration)
    Registration of the 'live_official_oi' tool with its schema (coin, hours, dex params) and handler that calls the /live/official-oi/{COIN} API endpoint.
    if (shouldRegister("live_official_oi")) server.registerTool(
      "live_official_oi",
      {
        description: "Official per-dex open interest for a coin, sourced from Hyperliquid's Info API (not derived from live_positions). Returns hourly snapshots with open interest, mark price, and 24h notional volume. Use when an agent needs venue-reported ground truth, per-dex breakdown, or wants to cross-check computed OI against official numbers. Default 7 days, max 30 days.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          coin: z.string().min(1).max(40).describe("Coin symbol (e.g. BTC, ETH, SOL). Use the bare ticker — dex is supplied via the 'dex' parameter, not prefix."),
          hours: z.number().min(1).max(720).default(168).describe("Number of hours of history (default 168 = 7 days, max 720 = 30 days)"),
          dex: z.enum(["hl", "xyz", "flx", "vntl", "hyna", "km", "abcd", "cash"]).optional().default("hl").describe("Which dex's official OI to return. Defaults to 'hl' (native Hyperliquid)."),
        },
      },
      async ({ useToonFormat, coin, hours, dex }) => {
        const params: Record<string, string> = { hours: String(hours) };
        if (dex) params.dex = dex;
        return toolResult(await callAPI(useToonFormat, `/live/official-oi/${coin.toUpperCase()}`, params));
      }
    );
  • Handler function for live_official_oi that constructs API request to /live/official-oi/{COIN} with hours and dex parameters, then returns the result.
    async ({ useToonFormat, coin, hours, dex }) => {
      const params: Record<string, string> = { hours: String(hours) };
      if (dex) params.dex = dex;
      return toolResult(await callAPI(useToonFormat, `/live/official-oi/${coin.toUpperCase()}`, params));
    }
  • Input schema for live_official_oi: useToonFormat (boolean), coin (string 1-40 chars), hours (number 1-720, default 168), dex (enum of dex names, default 'hl').
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        coin: z.string().min(1).max(40).describe("Coin symbol (e.g. BTC, ETH, SOL). Use the bare ticker — dex is supplied via the 'dex' parameter, not prefix."),
        hours: z.number().min(1).max(720).default(168).describe("Number of hours of history (default 168 = 7 days, max 720 = 30 days)"),
        dex: z.enum(["hl", "xyz", "flx", "vntl", "hyna", "km", "abcd", "cash"]).optional().default("hl").describe("Which dex's official OI to return. Defaults to 'hl' (native Hyperliquid)."),
      },
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It reveals the data is sourced from an external API, returns hourly snapshots, and includes specific data fields. It does not mention rate limits, authentication, or potential delays, but the core behavior is transparent. No contradictions with annotations (none exist).

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 plus a usage sentence, all highly relevant and front-loaded. The first sentence states purpose and source, the second describes output, and the third gives usage guidance. Every sentence adds value, no redundant content.

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 tool has no output schema, so the description must explain what is returned. It does so by listing 'hourly snapshots with open interest, mark price, and 24h notional volume.' However, it does not describe the exact structure (e.g., data types, timestamps format, or pagination). For a data retrieval tool with 4 parameters, the description is fairly complete but could be enhanced with output format details.

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%, and each parameter already has a clear description in the schema (coin, hours, dex, useToonFormat). The tool description adds general context about what the tool returns, but does not provide additional semantics beyond the schema for the parameters themselves. Per guidelines, baseline 3 is appropriate when schema already covers 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 provides 'official per-dex open interest for a coin' and distinguishes it from computed OI ('not derived from live_positions'). It specifies the data source (Hyperliquid's Info API) and the exact data returned (hourly snapshots with open interest, mark price, 24h notional volume). This leaves no ambiguity about the tool's function and differentiates it from siblings like live_oi_history.

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 explicitly states when to use the tool: 'when an agent needs venue-reported ground truth, per-dex breakdown, or wants to cross-check computed OI against official numbers.' It also notes the default and maximum time range (7 days default, 30 days max). While it doesn't explicitly list when not to use, the usage context is clear and helps agents decide among siblings.

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/Coinversaa/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server