Skip to main content
Glama
Bybit MCP Server

Bybit MCP Server

Official

getTradeAutoRepay

Read-only

Retrieves the authenticated Unified account's saved trade auto-repayment switch, showing whether account-wide auto repayment is enabled for Cross and Portfolio margin modes.

Instructions

Retrieve the authenticated Unified account's saved setting for trade auto repayment. result.autoRepay is "1" for enabled or "0" for disabled; this does not report whether any individual trade triggered repayment. Trade auto repayment runs only in Cross and Portfolio margin modes; an enabled saved setting has no effect in Isolated mode. This account-wide switch is separate from scheduled auto repayment queried by getSpotMarginTradeAutoRepayMode. Locally limited to 50 requests per rolling second per path within one MCP process. Business failures surface as MCP tool errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getTradeAutoRepay"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.28

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the exact return encoding ('1'/'0'), a critical caveat that it does not report per-trade repayment events, the margin-mode scoping of the setting, a rate limit of 50 requests per rolling second per path per MCP process, and that business failures surface as MCP tool errors. This is substantially more than the annotations carry.

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?

Sentences are front-loaded and each contributes a distinct fact: what is read, how to interpret the value, what it does not mean, mode constraints, sibling differentiation, limits, and error shape. It is dense but no sentence is padding, though the rate-limit and error notes could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so precisely by defining result.autoRepay. Combined with mode restrictions and error semantics, an agent has everything needed to call and interpret this tool correctly.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly implies the account is derived from authentication rather than an argument.

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?

The description opens with a specific verb and resource: 'Retrieve the authenticated Unified account's saved setting for trade auto repayment.' It then names the sibling it is not (getSpotMarginTradeAutoRepayMode, which queries scheduled auto repayment), so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the conditions under which the setting matters (Cross and Portfolio margin only; no effect in Isolated mode) and routes the agent away from the similarly named scheduled-repayment query. It does not explicitly point to setTradeAutoRepay as the mutation counterpart, so the guidance is clear but not fully exhaustive.

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