Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getIndexPriceKline

Query historical index price klines from the composite spot price across exchanges to analyze index price movements or compare with mark price for basis analysis.

Instructions

Query historical index price klines derived from the composite spot price across multiple exchanges.

Use this endpoint when you need to:

  • Analyze historical index price movements for research or backtesting

  • Compare index price vs mark price to understand basis spread over time

  • Build charts of the underlying spot market price reference used by Bybit

Supported Products: USDT contract, USDC contract, Inverse contract

Each kline entry is a 5-element array: [startTime, open, high, low, close]. Data is returned in reverse chronological order (most recent first).

Do not use this endpoint for trading price candles — use getMarketKline instead. Do not use this endpoint for mark price candles — use getMarkPriceKline instead.

Notes:

  • Data is returned in reverse chronological order (most recent first)

  • No authentication required

Agent hint: Use this endpoint to retrieve historical index price candles (composite spot price reference). For regular OHLCV trading price candles use getMarketKline. For mark price candles use getMarkPriceKline. For premium index (funding basis) candles use getPremiumIndexPriceKline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNolinear
symbolYes
intervalYes
startNo
endNo
limitNo
Behavior4/5

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

Discloses data format (5-element array), reverse chronological order, supported products, and no authentication required. Lacks rate limits or pagination details, but for a historical query tool, this is sufficient. No contradictions with annotations (none provided).

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?

Well-organized with clear sections (purpose, use cases, supported products, data format, exclusions, notes, agent hint). Each sentence adds value; no redundancy. Ideal length for this complexity.

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 output format (5-element array), ordering, authentication, and product support. No output schema is present, but the description explains the output adequately. Lacks details on parameter semantics and does not mention error cases, but overall complete for a read-only historical data tool.

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

Parameters2/5

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

Schema description coverage is 0%. The description does not explain individual parameters beyond implying symbol and interval are needed. Category, start, end, and limit are not described. This is a significant gap as the description fails to compensate for the missing schema descriptions.

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 it queries historical index price klines from composite spot prices. It explicitly lists when to use and distinguishes from sibling tools (getMarketKline, getMarkPriceKline, getPremiumIndexPriceKline), making the purpose unambiguous.

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?

Provides three concrete use cases (research/backtesting, basis spread comparison, charting) and explicit 'do not use' instructions with alternatives. Agent hint repeats guidance. Highly actionable.

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