Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

get_open_interest

Read-only

Get open interest by symbol, category, and interval. Supports pagination and time range filtering for market analysis.

Instructions

Get open interest for each symbol.

    Args:
        category: Product type - linear, inverse
        symbol: Symbol name (e.g. BTCUSDT)
        intervalTime: Interval - 5min, 15min, 30min, 1h, 4h, 1d
        startTime: Start timestamp in milliseconds
        endTime: End timestamp in milliseconds
        limit: Limit for data size per page (max 200, default 50)
        cursor: Pagination cursor
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
symbolYes
endTimeNo
categoryYes
startTimeNo
intervalTimeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnly and openWorld hints; description adds no further behavioral context, such as pagination behavior or data freshness.

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

Conciseness3/5

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

The description includes a purpose sentence and a parameter list, but the list format is verbose and repeats information from the schema names. Could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description adequately explains input parameters, but lacks contextual guidance such as typical use cases or data interpretation. Adequate but not comprehensive.

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 provides parameter explanations and examples for category and intervalTime, adding value beyond schema. However, other parameters like startTime and endTime lack explanatory text.

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 verb 'Get' and resource 'open interest for each symbol', distinguishing it from sibling data retrieval tools like get_kline or get_orderbook.

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

Usage Guidelines2/5

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

No usage guidelines provided; does not indicate when to use this tool versus alternatives like get_kline or get_funding_rate_history.

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

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