Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_kline

Retrieve historical kline data for any trading pair, including open, high, low, close prices, volume, and turnover, with customizable intervals and categories.

Instructions

Get kline/candlestick data.

Args: symbol: The trading pair, e.g., BTCUSDT. interval: Kline interval: 1,3,5,15,30,60,120,240,360,720,D,M,W (default: 60). category: Product type: spot, linear, inverse (default: spot). limit: Number of records (default: 100, max: 1000).

Returns: List of kline data [startTime, openPrice, highPrice, lowPrice, closePrice, volume, turnover].

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": "get_kline"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
intervalNo60
categoryNospot
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return format as a list of kline data with specific fields, and explains default values for parameters. However, it does not mention auth requirements, rate limits, or potential side effects, which would be helpful for transparency.

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 well-organized with Args and Returns sections, and each parameter is described in a single line. It is concise without unnecessary words, making it easy to parse.

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?

Given no output schema, the description provides a thorough explanation of the return value format. It covers all parameters, their defaults, and the exact structure of returned data, making the tool's behavior fully understandable.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description fully compensates by explaining each parameter's meaning, defaults, and allowed values (e.g., interval options). It also describes the return fields, providing complete semantic context beyond the schema.

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?

The description clearly states 'Get kline/candlestick data' and lists relevant parameters, making the purpose unambiguous. However, it does not explicitly differentiate from similar sibling tools like get_index_price_kline or get_mark_price_kline, which could confuse an AI agent.

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 guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or contextual hints. The description simply lists parameters and return format without addressing appropriate use cases.

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

Deploy Server

Other Tools