Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

subscribeSystemStatus

Read-only

Subscribe to Bybit system status push notifications to stay informed about maintenance, outages, and service health. Configure timeout and message count to control how long and how many updates are received.

Instructions

订阅系统状态推送

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
messageCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

C2.7/5.0
Behavior2/5

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

The annotations declare readOnlyHint and openWorldHint, but the description adds no behavioral context beyond a literal restatement. It does not explain how the subscription behaves, when it stops, whether it returns a single batch or a continuous stream, or what a 'push' entails.

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 extremely compact and front-loaded with the core purpose. It has no filler or redundant elaboration, though its brevity leaves significant behavioral and usage information unstated.

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 no output schema, the description omits essential context such as what the returned payload looks like, how timeoutMs and messageCount interact, and how an agent should interpret the subscription result. The tool is simple enough that the defaults allow basic invocation, but the description is incomplete for correct result handling.

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 does not explain timeoutMs or messageCount. Although the parameter names and schema defaults/minimums give some hints, the description adds no meaning about how these parameters affect subscription behavior.

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 the action and resource: subscribing to system status pushes. It is understandable and matches the tool name, but it does not differentiate this subscription from the many other subscribe* sibling tools.

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 about when to use this tool instead of related subscriptions such as subscribeTickers, subscribeOrderbook, or subscribeWallet. The description does not mention scenarios, prerequisites, or conditions for choosing this tool.

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