bybit-mcp

Overview Schema Source Related Servers Discussions Admin

switch_position_mode

Switch position mode between one-way and hedge mode for a trading pair on Bybit. Specify symbol, mode (0 or 3), and optional category and coin.

Instructions

Switch position mode between one-way and hedge mode.

Args: symbol: The trading pair, e.g., BTCUSDT. mode: Position mode: 0 (merged single side), 3 (both sides). category: Product type: linear, inverse (default: linear). coin: Required for inverse. Coin name, e.g., BTC.

Returns: Position mode switch result.

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": {
      "symbol": "<symbol>",
      "mode": "<mode>"
    },
    "name": "switch_position_mode"
  }
}

Input Schema

Name	Required	Default
`symbol`	Yes
`mode`	Yes
`category`	No	linear
`coin`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It states it switches mode (a mutating action) but does not disclose side effects, authorization needs, or error conditions. Minimal transparency beyond the action itself.

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

Conciseness3/5

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

Description includes a docstring-style argument list that is functional but slightly verbose. The purpose is front-loaded, but the argument details could be more streamlined. No unnecessary words, but not optimally concise.

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?

No output schema, and the return description 'Position mode switch result' is vague. Lacks details on response structure, error handling, or confirmation. Given the tool's complexity, more completeness is needed.

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 coverage, description explains all four parameters: symbol (example), mode (0=merged single side, 3=both sides), category (default linear), and coin (required for inverse). Adds meaning beyond the raw schema.

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?

Description explicitly states 'Switch position mode between one-way and hedge mode', clearly identifying the verb and resource. It distinguishes the tool's function from basic order placement but does not explicitly differentiate from sibling tools like set_margin_mode or set_leverage.

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 on when to use this tool vs alternatives. Does not specify prerequisites, such as needing an existing position or being in a specific account mode. The description lacks any context about appropriate scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server