Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_dcp

Set automatic order cancellation when connection is lost. Specify time window in seconds and product type to protect your open orders.

Instructions

Set Disconnect Cancel All (DCP) - auto-cancel orders on disconnect.

Args: time_window: Time window in seconds (3-300). product: Product type: OPTIONS, DERIVATIVES, SPOT (default: OPTIONS).

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": {
      "time_window": "<time_window>"
    },
    "name": "set_dcp"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_windowYes
productNoOPTIONS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure burden. It reveals that setting DCP will auto-cancel orders on disconnect and provides valid ranges for time_window (3-300 seconds) and product options. However, it does not mention permissions, side effects (e.g., overriding existing DCP), or error conditions, leaving gaps.

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

Conciseness5/5

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

The description is short, front-loaded with purpose ('Set Disconnect Cancel All (DCP) - auto-cancel orders on disconnect.'), and includes only necessary parameter details. Every sentence contributes meaning without redundancy.

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

Completeness3/5

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

Given the tool has 2 parameters, no output schema, and no annotations, the description provides core purpose and parameter details but lacks information on return values, error handling, or confirmation. It is adequate for a simple setter but could be more complete.

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?

Schema description coverage is 0%, so the description must add meaning. It specifies that time_window is in seconds with range 3-300, and product defaults to OPTIONS with options listed (OPTIONS, DERIVATIVES, SPOT). This adds significant value beyond the schema, which only has type and title.

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 clearly states 'Set Disconnect Cancel All (DCP) - auto-cancel orders on disconnect.' This uses a specific verb ('Set') and resource ('Disconnect Cancel All'), and the phrase 'auto-cancel orders on disconnect' differentiates it from sibling tools like set_leverage or set_margin_mode.

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

Usage Guidelines3/5

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

The description implies usage by describing what the tool does, but it does not explicitly state when to use it versus alternatives. Among siblings, there is get_dcp_info which retrieves DCP settings, but no direct alternative for setting DCP. No when-not or exclusion criteria are provided.

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