Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

get_kline

Read-only

Retrieve historical candlestick data for any symbol on Bybit. Specify product type, symbol, interval, and optional time range.

Instructions

Query kline/candlestick data.

    Args:
        category: Product type - spot, linear, inverse
        symbol: Symbol name (e.g. BTCUSDT)
        interval: Kline interval - 1,3,5,15,30,60,120,240,360,720,D,M,W
        start: Start timestamp in milliseconds
        end: End timestamp in milliseconds
        limit: Limit for data size per page (max 200, default 200)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
limitNo
startNo
symbolYes
categoryYes
intervalYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's burden is lower. It does not add behavioral context like pagination behavior or rate limits; thus a baseline 3 is appropriate.

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?

The description is structured as a docstring with an Args section, making it easy to parse. It is informative without being overly verbose, though could be slightly more concise.

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?

Given the tool has 6 parameters and an output schema, the description explains all parameters adequately. It does not discuss the output, but that is covered by the output schema. A small gap is the lack of usage context.

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?

Schema description coverage is 0%, but the description provides detailed explanations for each parameter (e.g., category options, interval values, timestamps). This adds significant meaning beyond the bare schema.

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 'Query kline/candlestick data', using a specific verb and resource. It distinguishes from sibling tools like get_tickers or get_orderbook, which serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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