Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

market_historical_oi

Retrieve historical hourly open interest snapshots (notional USD) for a specific coin or the global exchange aggregate, with a maximum range of 30 days.

Instructions

Get historical hourly open interest snapshots (notional USD). Supports per-coin filtering or global exchange aggregation. Max range is 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
coinNoFilter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER). Omit for global exchange aggregate.
sinceNoTime window for history (max 30d). e.g. '24h', '7d', '30d'
startTimeNoExplicit start time (ISO string or timestamp). Overrides 'since'.
endTimeNoExplicit end time (ISO string or timestamp). Defaults to now.

Implementation Reference

  • src/index.ts:919-937 (registration)
    Registration of the market_historical_oi tool on the MCP server. Uses server.tool() (not server.registerTool()), meaning it's always registered regardless of API key presence. The tool fetches historical hourly open interest snapshots from the /market/historical-oi API endpoint.
    if (shouldRegister("market_historical_oi")) server.tool(
      "market_historical_oi",
      "Get historical hourly open interest snapshots (notional USD). Supports per-coin filtering or global exchange aggregation. Max range is 30 days.",
      {
        useToonFormat: useToonFormatSchema,
        coin: z.string().optional().describe("Filter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER). Omit for global exchange aggregate."),
        since: sinceSchema.optional().describe("Time window for history (max 30d). e.g. '24h', '7d', '30d'"),
        startTime: z.string().optional().describe("Explicit start time (ISO string or timestamp). Overrides 'since'."),
        endTime: z.string().optional().describe("Explicit end time (ISO string or timestamp). Defaults to now."),
      },
      async ({ useToonFormat, coin, since, startTime, endTime }) => {
        const params: Record<string, string> = {};
        if (since) params.since = since;
        if (startTime) params.startTime = startTime;
        if (endTime) params.endTime = endTime;
        if (coin) params.coin = normalizeCoin(coin);
        return toolResult(await callAPI(useToonFormat, "/market/historical-oi", params));
      }
    );
  • Input schema for the market_historical_oi tool. Accepts: useToonFormat (bool), coin (optional symbol filter), since (optional time window string like '24h'), startTime (optional ISO override for since), endTime (optional end bound, defaults to now).
    {
      useToonFormat: useToonFormatSchema,
      coin: z.string().optional().describe("Filter by coin symbol (e.g. BTC, ETH, SOL). For builder dex: prefix:COIN (e.g. xyz:SILVER). Omit for global exchange aggregate."),
      since: sinceSchema.optional().describe("Time window for history (max 30d). e.g. '24h', '7d', '30d'"),
      startTime: z.string().optional().describe("Explicit start time (ISO string or timestamp). Overrides 'since'."),
      endTime: z.string().optional().describe("Explicit end time (ISO string or timestamp). Defaults to now."),
    },
  • Handler function for market_historical_oi. Builds query params from inputs (since, startTime, endTime, coin with normalizeCoin), then calls the API helper to GET /market/historical-oi on the Coinversa API.
    async ({ useToonFormat, coin, since, startTime, endTime }) => {
      const params: Record<string, string> = {};
      if (since) params.since = since;
      if (startTime) params.startTime = startTime;
      if (endTime) params.endTime = endTime;
      if (coin) params.coin = normalizeCoin(coin);
      return toolResult(await callAPI(useToonFormat, "/market/historical-oi", params));
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read operation and adds constraints like max 30 days, but does not disclose response format, rate limits, or auth requirements. It is adequate but not comprehensive.

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, front-loading the core action and resource, then adding key constraints. Every sentence is informative with zero fluff.

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?

For a tool with 5 parameters and no output schema, the description covers the resource, filters, and time constraints. It does not describe the return structure, but the context is sufficient for basic understanding.

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 description coverage is 100%, so the baseline is 3. The description adds no additional information beyond what the schema already provides for each parameter; it merely summarizes.

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 specific verb 'Get' and resource 'historical hourly open interest snapshots (notional USD)'. It distinguishes from sibling tools like live_oi_history and live_official_oi by emphasizing 'historical hourly' and aggregation options.

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

Usage Guidelines3/5

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

The description mentions per-coin filtering and global aggregation, but does not explicitly state when not to use this tool or compare alternatives. It provides context for usage but lacks exclusionary 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/Coinversaa/mcp-server'

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