Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getOpenInterest

Query historical open interest for derivative contracts at intervals from 5min to 1d. Analyze market sentiment by tracking changes in position size over time.

Instructions

Query historical open interest data for derivative contracts at specified time intervals. Returns the total outstanding position size across all market participants.

Use this endpoint when you need to:

  • Track changes in open interest over time as a market sentiment indicator

  • Analyze open interest trends relative to price movements for research

  • Retrieve open interest time series at intervals of 5min, 15min, 30min, 1h, 4h, or 1d

Supported Products: USDT contract, USDC contract, Inverse contract

Supports cursor-based pagination via nextPageCursor.

Do not use this endpoint for current open interest — use getTickers which includes openInterest and openInterestValue in real-time.

Notes:

  • Data may experience increased latency during extreme market volatility

  • Supports cursor-based pagination

  • No authentication required

Agent hint: Use this endpoint to retrieve historical open interest time series data. Required parameters: category, symbol, and intervalTime (5min/15min/30min/1h/4h/1d). For current open interest value, use getTickers which includes openInterest in real-time. For pagination, pass nextPageCursor from the previous response into the cursor parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
symbolYes
intervalTimeYes
startTimeNo
endTimeNo
limitNo
cursorNo
Behavior5/5

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

Discloses important behaviors: historical data only, cursor-based pagination, potential latency during volatility, no authentication required. These details go beyond the minimal and inform the agent of operational characteristics.

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 efficiently structured with introductory paragraph, bullet points for use cases, clear notes, and an agent hint. Every sentence adds value, no redundancy, and it's front-loaded with the core purpose.

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?

Covers key aspects: purpose, parameters, pagination, latency, products, and alternative tool. Lacks explicit response structure description, but given no output schema, the description still provides sufficient context for an agent to use the tool correctly.

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?

With 0% schema description coverage, the description compensates by naming required parameters (category, symbol, intervalTime) and explaining interval values, cursor pagination. Leaves startTime, endTime, limit somewhat ambiguous but provides essential guidance.

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 queries historical open interest data and returns total outstanding position size. It distinguishes itself by specifying 'historical' and contrasting with getTickers for real-time data, which avoids confusion with siblings.

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 lists use cases (track changes, analyze trends) and provides a clear 'Do not use' directive with alternative tool (getTickers). Also lists supported intervals and products, offering comprehensive when-to-use 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/bybit-exchange/trading-mcp'

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