Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

manual_repay

Repay loans manually on Bybit, optionally specifying coin and amount; supports automatic conversion of assets if needed.

Instructions

Manual repay (with auto conversion if needed).

Args: coin: Coin to repay (optional). amount: Repay amount (optional).

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": "manual_repay"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNo
amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

The description adds the key behavioral trait of auto conversion 'if needed', which is beyond the schema. However, it does not disclose what happens when both parameters are omitted, potential side effects, or authorization requirements. With no annotations, the description partially compensates but lacks depth.

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 very short and uses a clean 'Args:' structure, making it easy to parse. It avoids unnecessary words, but the brevity comes at the cost of completeness, which is acceptable for conciseness.

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 the tool has two optional parameters and no output schema, the description should provide more context about the return value, error handling, or typical use cases. It only describes the basic action, leaving significant gaps for an agent to infer.

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 coverage is 0%, so the description must compensate, but it only provides minimal labeling: 'Coin to repay (optional)' and 'Repay amount (optional)'. This adds basic meaning but fails to explain formats, constraints, or defaults beyond the schema's empty strings.

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 it is a 'Manual repay' with auto conversion, which identifies the verb and resource. It also distinguishes itself from the sibling 'manual_repay_no_convert' by mentioning auto conversion. However, the exact resource being repaid (e.g., margin loan, crypto loan) is not specified, leaving slight ambiguity.

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 is provided on when to use this tool versus alternatives like 'repay_liability' or 'crypto_loan_repay'. There are no prerequisites, conditions, or exclusions mentioned, leaving the agent without decision-making 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