Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

batch_set_collateral_coin

Batch enable or disable collateral for multiple coins. Provide a list of coins and desired collateral switch state.

Instructions

Batch set collateral coin on/off.

Args: request: List of objects, each with: coin (string), collateralSwitch ("ON"/"OFF").

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": {
      "request": "<request>"
    },
    "name": "batch_set_collateral_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided; description discloses it is a write operation but lacks details on side effects, permissions, rate limits, idempotency, or error handling. Significant gaps for a mutating batch 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?

Three lines with clear, front-loaded purpose and concise parameter documentation. No extraneous information.

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, annotations, or details on return value, behavior on failure, or batch semantics (e.g., partial success). Description leaves agent uninformed about important operational aspects.

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?

Input schema has 0% coverage (just array of objects with additionalProperties). Description adds critical structure: each object requires 'coin' (string) and 'collateralSwitch' ('ON'/'OFF'), significantly compensating for schema lack. Could be slightly more precise (e.g., enum for switch).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'Batch set' and resource 'collateral coin', clearly distinguishing from sibling 'set_collateral_coin' (singular) by indicating batch operation.

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 batch setting via the name and parameter description, but does not explicitly state when to use this tool over alternatives (e.g., for single coin use set_collateral_coin), nor provides exclusions or context.

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