Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

getFMartDetail

Read-only

Retrieve the full status and performance of a futures Martingale bot, including configuration, PnL metrics, position details, margin balances, and round progress.

Instructions

Retrieves comprehensive details for a specific futures Martingale bot, including configuration (symbol, mode, leverage, price trigger, add position settings), current display status, PnL metrics (realized, unrealized, total), position info (size, average price, balances), round progress (completed rounds, current round, current adds), margin balances, and timestamps.

The bot_id is a numeric ID obtained from createFMartBot 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 Martingale bot. The response contains all PnL fields, position details, round progress (completed_rounds, current_round, current_added_pos_num), 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.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, and the description adds rate-limit details (10 rps per UID), notes the bot_id source, and discloses that a close reason is included if the bot has stopped. This is valuable behavioral context beyond the read-only annotation, though it stops short of a detailed response contract.

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 purpose and key content, and the bot_id source and rate limit are useful standalone facts. Some redundancy exists between the initial field list and the 'Agent hint' (PnL fields and round progress are repeated), so it is not maximally lean.

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?

With no output schema, the description carries the burden of explaining the return value and does so broadly: PnL metrics, position details, round progress, margin balances, timestamps, and stopped-bot close reason. It is sufficiently complete for a single-parameter read-only detail endpoint, though exact response shape is not specified.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explaining that bot_id is a numeric ID obtained from createFMartBot or bot listing endpoints. This adds provenance and type clarification that the raw schema's anyOf pattern does not provide.

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 opens with a specific verb and resource: 'Retrieves comprehensive details for a specific futures Martingale bot,' then enumerates concrete content areas (configuration, PnL, position info, round progress, timestamps). This clearly differentiates it from nearby bot-management tools like createFMartBot, closeFMartBot, and getFMartLimit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Agent hint' explicitly says to use this endpoint to check status/performance and to 'Prefer this over other endpoints' for a specific bot's performance. It does not name sibling alternatives or state when not to use it, so it falls just short of fully explicit routing.

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