Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setCollateralSwitch

Enable or disable a coin's use as collateral on Bybit. Manage margin availability by switching the collateral status for any supported asset.

Instructions

Enable or disable specified coin as collateral

Agent hint: Error handling: 182012 means collateral services are unavailable in the user's region due to regulatory requirements — a region restriction, NOT a parameter problem, so do not retry and do not try a different coin. 182011 means the coin's collateral amount has reached the platform limit — suggest enabling collateral on another asset, or transferring in another supported asset as collateral.

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": {
      "coin": "<coin>",
      "collateralSwitch": "<collateralSwitch>"
    },
    "name": "setCollateralSwitch"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYes
collateralSwitchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already indicate this is a mutating, non-destructive operation. The description adds valuable behavioral context beyond annotations by explaining that error 182012 is a region restriction (do not retry or switch coins) and 182011 is a platform limit (suggest alternatives). This meaningfully helps the agent respond correctly to failures.

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 main purpose is stated in one concise, front-loaded sentence. The Agent hint is longer but each part addresses a distinct error code with a clear recommended action, so every sentence earns its place.

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 covers the core action and two important failure modes, which is helpful for a simple two-parameter tool. It is missing guidance on how this tool relates to setBatchCollateralSwitch and does not clarify prerequisites or side effects, leaving the context adequate but incomplete.

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?

Schema description coverage is 0%, so the description must compensate, but it only paraphrases the parameter names: 'specified coin' and 'enable or disable.' It does not explain the expected format of coin (e.g., symbol like BTC) or add meaning beyond what the schema's enum already provides for collateralSwitch.

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 action ('Enable or disable') and the target object ('specified coin as collateral'), so an agent can tell what the tool does. However, it does not explicitly differentiate itself from the closely related sibling setBatchCollateralSwitch, so it misses the top score.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as setBatchCollateralSwitch or getCollateralInfo. The 'Agent hint' covers how to interpret two error codes, but it does not help an agent decide when to invoke this tool in the first place.

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