Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_auto_add_margin

Set auto add margin for Bybit positions by toggling on or off. Specify symbol, category, and position index to control automatic margin allocation.

Instructions

Set auto add margin for a position.

Args: symbol: Symbol, e.g., BTCUSDT. auto_add_margin: 0: off, 1: on. category: Product type: linear (default: linear). position_idx: 0: one-way, 1: hedge-Buy, 2: hedge-Sell (default: 0).

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>",
      "auto_add_margin": "<auto_add_margin>"
    },
    "name": "set_auto_add_margin"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
auto_add_marginYes
categoryNolinear
position_idxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action (set auto-add margin) and parameter values, but does not explain consequences like effects on margin balance, liquidation prevention, or reversibility, which is insufficient for a mutation tool.

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 extremely concise: a one-line purpose followed by a clear parameter list in a standard docstring format. Every sentence is necessary and front-loaded, with no wasted words.

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 lack of output schema and annotations, the description covers parameter details but omits context such as prerequisites (e.g., position existence), return values, or side effects. It is adequate but not fully comprehensive for an agent to use without additional knowledge.

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, the description adds significant value by explaining each parameter's meaning and allowed values (e.g., auto_add_margin: 0 off, 1 on; position_idx: 0 one-way, 1 hedge-Buy, 2 hedge-Sell). This compensates well for the schema gaps.

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 tool's purpose: 'Set auto add margin for a position.' It uses a specific verb and resource, but does not explicitly differentiate it from sibling tools like 'add_reduce_margin' or 'set_margin_mode', which limits clarity in distinguishing use cases.

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?

There is no guidance on when to use this tool versus alternatives. No context about prerequisites, such as requiring an open position or an appropriate account type, leaving the agent without information on selection criteria.

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