Skip to main content
Glama

Open interest change

open_interest_change
Read-only

How one asset's perpetual-futures open interest moved over the last 1, 4 and 24 hours on OKX, dYdX and Kraken Futures (the US-reachable venues that publish OI history): current OI in coins, change and % change per window with the price change alongside, the conventional reading (e.g. OI up with price down, typically read as new shorts), and a combined view across venues. Hourly samples. Accepts BTC, BTCUSDT, BTC/USDT or XBT. Venues that fail are listed under errors; the call fails (and is not charged) only if none answers. Costs $0.003 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "open_interest_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesBase asset or pair, e.g. 'BTC', 'ETH', 'SOLUSDT'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing sampling frequency (hourly), partial-failure behavior (failed venues listed under errors; call fails and is not charged only if none answers), and an explicit price of $0.003 USDC per call. That is exactly the cost and failure context an agent needs before invoking a paid, open-world read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core answer (what moved, on which venues, over which windows) and the operational notes (errors, cost) come last where they belong. It is a single dense sentence-chain with no filler, though the parenthetical venue justification and example interpretation slightly lengthen it.

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?

With no output schema, the description fully compensates by outlining the return payload: current OI in coins, change and percent change per window, the accompanying price change, the conventional reading, a combined cross-venue view, and an errors list. Nothing required to call or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real value by enumerating interchangeable symbol forms (BTC, BTCUSDT, BTC/USDT, XBT) that the schema's example list does not cover. It adds no information about normalization or case handling beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — perpetual-futures open interest movement — with the exact venues (OKX, dYdX, Kraken Futures) and windows (1h, 4h, 24h). It does not name a sibling such as perp_market_overview to contrast against, but the scope is narrow enough that an agent can distinguish it without opening the schema.

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 implies when it is useful by explaining the conventional reading (OI up with price down = new shorts), which tells the agent this is an interpretive positioning tool. However, it never says when not to use it or which sibling to pick for related questions like liquidations or funding, so usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources