Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_leverage

Define buy and sell leverage values for a trading pair on Bybit. Specify symbol, leverage amounts, and product type to adjust margin requirements.

Instructions

Set leverage for a symbol.

Args: symbol: The trading pair, e.g., BTCUSDT. buy_leverage: Buy side leverage, e.g., "10". sell_leverage: Sell side leverage, e.g., "10". category: Product type: linear, inverse (default: linear).

Returns: Leverage setting 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>",
      "buy_leverage": "<buy_leverage>",
      "sell_leverage": "<sell_leverage>"
    },
    "name": "set_leverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
buy_leverageYes
sell_leverageYes
categoryNolinear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral traits such as side effects, required permissions, or whether the change is irreversible. Merely stating 'Set leverage' 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.

Conciseness4/5

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

The description is concise with a clear structure (Args and Returns sections). Every sentence adds value, though it could be slightly more compact.

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?

The description explains parameters well but lacks context about prerequisites, response format details, and when to use this tool among many siblings. For a parameter count of 4 and no output schema, 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?

The description adds meaningful context for each parameter, including examples and default values, compensating for the 0% schema description coverage. It clarifies the meaning of symbol, buy_leverage, sell_leverage, and category.

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 that the tool sets leverage for a symbol, with examples. However, it does not differentiate from sibling tools like set_margin_mode or set_spot_margin_leverage, which could confuse an AI agent.

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 for setting leverage but lacks explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites or when not to use it.

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