Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

subscribeRfqPublicTrades

Read-only

Subscribe to Bybit RFQ public trade updates in real time. Set a timeout and message count to receive and process trade events as they occur.

Instructions

订阅 RFQ 公开成交

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "subscribeRfqPublicTrades"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
messageCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and external-data profile. The description adds the public RFQ trade scope, which is useful context, but it does not explain the subscription lifecycle (how timeoutMs and messageCount terminate the call) or the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and free of filler, but it is under-specified rather than efficiently complete. A subscription tool with two behavior-affecting parameters needs more than a six-character phrase.

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?

With no output schema and many near-identical subscription siblings, the description should clarify what data is returned and how this subscription terminates or differs from siblings. It does neither, so the definition is not complete enough for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description provides no information about timeoutMs or messageCount. It does not compensate for the lack of schema descriptions, leaving the agent to rely entirely on parameter names and defaults.

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 says '订阅 RFQ 公开成交' — subscribe to RFQ public trades — so the verb and resource are explicit. It conveys the core function but does not distinguish itself from closely related sibling tools like subscribeRfqTrades or subscribePublicTrade.

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?

There is no when-to-use statement, no exclusions, and no pointer to any alternative subscription tool. Given the long sibling list of similar RFQ/public trade subscriptions, an agent must guess when this one is appropriate.

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