Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_spot_margin_auto_repay_mode

Enable or disable automatic repayment of spot margin loans. Optionally specify currency.

Instructions

Set spot margin auto repay mode.

Args: auto_repay_mode: Auto repay mode: on, off. 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": {
      "auto_repay_mode": "<auto_repay_mode>"
    },
    "name": "set_spot_margin_auto_repay_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
auto_repay_modeYes
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It does not mention any side effects, permission requirements, rate limits, or what happens to existing margin positions when the mode is changed. The tool name implies mutation, but no transparency is provided.

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 front-loaded purpose and a structured 'Args' section. No redundant words, but it could be more structured (e.g., bullet points) and include broader context.

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?

Given no output schema and no annotations, the description is incomplete. It fails to explain the tool's effect on the user's account, prerequisites, or how it integrates with other spot margin features. A more comprehensive description is needed for safe and correct usage.

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

Parameters3/5

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

Schema description coverage is 0%. The description adds meaning by listing allowed values for 'auto_repay_mode' (on, off) and noting that 'currency' is optional. However, it does not explain the meaning of 'on' vs 'off' or provide any constraints on the currency parameter.

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 'Set spot margin auto repay mode', which is a specific verb+resource pair. It distinguishes from the sibling 'get_spot_margin_auto_repay_mode' by being a write operation, but among many other 'set' tools, it lacks explicit differentiation.

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. For example, it doesn't explain prerequisites, when auto-repay should be turned on/off, or how it differs from manual repay tools.

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