Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getRpiOrderbook

Retrieve orderbook depth with separate RPI and non-RPI order sizes at each price level for market microstructure analysis.

Instructions

Retrieve orderbook depth data that explicitly shows RPI (Retail Price Improvement) order sizes at each price level, alongside regular non-RPI order sizes.

Use this endpoint when you need to:

  • Identify the RPI liquidity available at each price level separately from non-RPI liquidity

  • Distinguish between RPI and non-RPI order flow for market microstructure analysis

  • Access the full orderbook including RPI orders (which are excluded from the standard orderbook)

Supported Products: Spot, USDT contract, Inverse contract

Each price level returns a 3-element array: [price, non-RPI size, RPI size]. Returns up to 50 levels per side.

Do not use this endpoint if you only need regular orderbook depth — use getOrderbook instead.

Notes:

  • Each price level returns [price, non-RPI size, RPI size]

  • No authentication required

Agent hint: Use this endpoint when you specifically need RPI (Retail Price Improvement) order sizes in the orderbook. For standard orderbook depth without RPI breakdown, use getOrderbook instead. The response format differs from getOrderbook: each level has 3 values [price, non-RPI size, RPI size].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo
symbolYes
limitYes
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses supported products, response format (3-element arrays), limit of 50 levels per side, and no authentication required. It covers key behavioral traits but lacks details on rate limits or error handling.

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 well-structured with bullet points, sections, and clear headings. It front-loads the purpose. A minor redundancy (repeated array format) prevents a perfect score, but it remains concise and scannable.

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's complexity (3 parameters, no annotations, no output schema), the description covers supported products, response format, limit, and alternatives. It explains the RPI-specific feature well. However, it could clarify the category parameter enum values and provide a brief example response for completeness.

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?

Input schema has 0% description coverage, so the description must compensate. While it mentions supported products (mapping to category) and limit (max 50 levels), it does not explicitly describe each parameter or their formats. The agent must infer which parameter corresponds to product category and the meaning of symbol.

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 retrieves orderbook depth data with RPI order sizes, distinguishing it from the standard orderbook tool getOrderbook. It uses specific verbs and resources, and explicitly differentiates from 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?

The description provides explicit usage scenarios (e.g., needing RPI liquidity, microstructure analysis) and a clear 'Do not use' directive with the alternative getOrderbook. An agent hint reinforces when to use it.

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