Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

subscribeRpiOrderbook

Read-only

Subscribe to real-time RPI order book snapshots for Bybit markets, providing immediate access to order book depth data for trading decisions.

Instructions

订阅 RPI 订单薄快照

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

Input Schema

NameRequiredDescriptionDefault
symbolYes
categoryNolinear
timeoutMsNo
messageCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

C2.9/5.0
Behavior3/5

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

Beyond readOnlyHint/openWorldHint, the description adds that this is a snapshot feed ('快照'), implying messages are full snapshots rather than deltas. It does not disclose how timeoutMs/messageCount control the subscription lifecycle or what happens when limits are reached, but annotations cover the safety profile.

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?

One short sentence with no filler; the action and resource are front-loaded. Its brevity is a strength, though it omits information that other dimensions penalize.

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

Completeness2/5

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

For a subscription tool with four parameters and no output schema, the description is too thin: it does not explain subscription lifecycle, parameter behavior, return/stream format, or relationship to REST alternatives. The minimal purpose is clear, but an agent lacks enough to call it confidently in varied contexts.

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% and the description adds no parameter-specific meaning. Names like timeoutMs and messageCount are somewhat self-explanatory and the category enum provides constraints, but the exact interaction semantics remain ambiguous.

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 states a clear verb ('订阅'/'subscribe') and a specific resource ('RPI 订单薄快照'). This separates it from generic orderbook tools but does not explicitly distinguish it from getRpiOrderbook or clarify the streaming vs REST distinction.

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 when-to-use guidance, no alternatives, and no conditions for choosing this over getRpiOrderbook or subscribeOrderbook. Only the verb '订阅' implies real-time subscription; what situations call for it is left to inference.

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