Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_spot_margin_leverage

Set the spot margin leverage for a currency to control position size and risk in margin trading.

Instructions

Set spot margin leverage.

Args: leverage: Leverage value, e.g., "2". currency: Currency (optional).

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": {
      "leverage": "<leverage>"
    },
    "name": "set_spot_margin_leverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
leverageYes
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description must carry the burden of behavioral transparency. It simply states 'Set spot margin leverage' without disclosing effects, requirements, safety considerations, or implications of changing leverage.

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 brief with two short sentences and a concise parameter list. However, it could be slightly more structured with explicit notes on parameter constraints.

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; the description is minimal for a tool that modifies margin leverage, which likely has financial implications. Lacks context on prerequisites, side effects, or relation to other settings.

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

Parameters2/5

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

The description adds an example for leverage ('e.g., "2"') but no range, allowed values, or format. Currency is marked optional without explanation. With 0% schema coverage, the description does not sufficiently compensate.

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 states 'Set spot margin leverage', clearly indicating the action (set) and the resource (spot margin leverage). It distinguishes from the sibling tool 'set_leverage' by specifying 'spot margin', but does not elaborate on what spot margin leverage entails.

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 versus alternatives such as 'set_leverage' or other spot margin settings. The description only lists parameters without contextual usage advice.

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