Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

live_oi_history

Fetch historical open interest for Hyperliquid coins or global OI to detect accumulation, distribution, and market conviction shifts.

Instructions

Get historical open interest data for any coin on Hyperliquid, or global OI across all coins. Best for identifying accumulation/distribution phases, market conviction shifts, and whether a move was backed by positioning. 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.
coinNoCoin symbol (e.g. BTC, ETH, SOL). Omit for global OI across all coins.
hoursNoNumber of hours of history (default 168 = 7 days, max 720 = 30 days)

Implementation Reference

  • src/index.ts:1003-1019 (registration)
    Registration of the 'live_oi_history' tool with the MCP server, including input schema definition for optional 'coin' (string) and 'hours' (number, default 168) parameters.
    if (shouldRegister("live_oi_history")) server.registerTool(
  "live_oi_history",
  {
    description: "Get historical open interest data for any coin on Hyperliquid, or global OI across all coins. Best for identifying accumulation/distribution phases, market conviction shifts, and whether a move was backed by positioning. Default 7 days, max 30 days.",
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      coin: z.string().optional().describe("Coin symbol (e.g. BTC, ETH, SOL). Omit for global OI across all coins."),
      hours: z.number().min(1).max(720).default(168).describe("Number of hours of history (default 168 = 7 days, max 720 = 30 days)"),
    },
  },
  async ({ useToonFormat, coin, hours }) => {
    if (coin) {
      return toolResult(await callAPI(useToonFormat, `/live/oi-history/${coin.toUpperCase()}`, { hours: String(hours) }));
    }
    return toolResult(await callAPI(useToonFormat, "/live/oi-history", { hours: String(hours) }));
  }
);
  • src/index.ts:1013-1018 (handler)
    Handler function for 'live_oi_history'. Calls the API at '/live/oi-history/{COIN}' if a coin is specified, otherwise calls '/live/oi-history' for global OI data. Delegates to the shared callAPI helper with retry/timeout logic.
    async ({ useToonFormat, coin, hours }) => {
  if (coin) {
    return toolResult(await callAPI(useToonFormat, `/live/oi-history/${coin.toUpperCase()}`, { hours: String(hours) }));
  }
  return toolResult(await callAPI(useToonFormat, "/live/oi-history", { hours: String(hours) }));
}
  • src/index.ts:1007-1011 (schema)
    Input schema for live_oi_history tool: optional 'coin' (string, e.g. BTC, ETH) and 'hours' (number, 1-720, default 168/7days) using Zod validation.
    inputSchema: {
  useToonFormat: useToonFormatSchema,
  coin: z.string().optional().describe("Coin symbol (e.g. BTC, ETH, SOL). Omit for global OI across all coins."),
  hours: z.number().min(1).max(720).default(168).describe("Number of hours of history (default 168 = 7 days, max 720 = 30 days)"),
},

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses that data is historical, with a default 7-day and max 30-day range. It also mentions output format option (toon format vs JSON), which is a behavioral detail. Could be more specific about data granularity, but sufficient for an agent.

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, no fluff. First sentence states purpose, second adds usage context and defaults. Well-structured and front-loaded with essential information.

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 no output schema and 3 parameters, description covers core: purpose, use cases, and parameter guidance. It mentions output format but does not detail return structure. The term 'toon format' may require domain knowledge, but overall it is reasonably complete for an agent familiar with sibling tools.

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. Description adds minimal value beyond schema: it reiterates default hours and mentions coin omission for global OI, which the schema already indicates via optionality. No new semantic information is provided.

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 verb 'Get', the resource 'historical open interest data', and the scope 'any coin on Hyperliquid, or global OI across all coins'. It distinguishes from siblings like live_official_oi by specifying historical nature and optional coin parameter.

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 explicit context: 'Best for identifying accumulation/distribution phases, market conviction shifts, and whether a move was backed by positioning.' It also notes defaults and limits, and advises using coin omission for global OI. However, it does not explicitly state when not to use this tool.

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