Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

getComboDetail

Read-only

Retrieve comprehensive details for a futures combo bot, including configuration, PnL metrics, positions, margin balances, and close reason. Use bot_id to check status and performance.

Instructions

Retrieves comprehensive details for a specific futures combo bot, including configuration (symbols, leverage, rebalancing mode), current display status, PnL metrics (total PnL, realized, unrealized, funding fee), portfolio position info, margin balances (total, available, margin balance), and timestamps.

The bot_id is a numeric ID obtained from createComboBot or bot listing endpoints.

Rate limit: 10 requests per second per UID.

Agent hint: Use this endpoint to check the status and performance of a combo bot. The response contains all PnL fields, position details, rebalancing stats, and close reason if the bot has stopped. Prefer this over other endpoints when answering questions about a specific bot's performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.20
    • addedInput schema / properties / bot_id / anyOf
      Added value: +[
+  {
+    "pattern": "^[0-9]+$",
+    "type": "string"
+  },
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  }
+]
    • removedInput schema / properties / bot_id / type
      Removed value: -"integer"
  2. First observedv2.1.11

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark this as read-only, and the description adds useful behavioral context beyond that: the response includes close reason if the bot has stopped, rebalancing stats, and the rate limit of 10 requests per second per UID. No contradiction with annotations.

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 front-loaded with a clear purpose and field summary, and the Agent hint adds actionable routing information. Slight redundancy exists: 'all PnL fields' repeats PnL details already enumerated earlier, so not perfectly 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?

For a single-parameter read-only endpoint with no output schema, the description covers what the caller gets, where the bot_id comes from, rate limiting, and the special close-reason behavior. This is sufficient for an agent to select and invoke the tool correctly.

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?

The schema only defines bot_id as a number-like value, but the description adds essential provenance: 'bot_id is a numeric ID obtained from createComboBot or bot listing endpoints.' With 0% schema description coverage and only one parameter, this fully compensates.

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?

States a specific verb and resource: 'Retrieves comprehensive details for a specific futures combo bot' and lists key field categories (configuration, PnL, portfolio, margin, timestamps). It clearly differentiates from sibling bot-detail tools by explicitly targeting combo bots and referencing createComboBot.

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 Agent hint gives explicit guidance: 'Use this endpoint to check the status and performance of a combo bot' and 'Prefer this over other endpoints when answering questions about a specific bot's performance.' This tells the agent exactly when this tool is the right choice among many alternatives.

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