Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

new_crypto_loan_flexible_repay_collateral

Repay a flexible crypto loan using your collateral. Provide the loan currency, collateral coin, and amount to complete the repayment.

Instructions

Repay flexible crypto loan with collateral.

Args: loan_currency: Loan currency. collateral_coin: Collateral coin. amount: Repay amount.

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": {
      "loan_currency": "<loan_currency>",
      "collateral_coin": "<collateral_coin>",
      "amount": "<amount>"
    },
    "name": "new_crypto_loan_flexible_repay_collateral"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_currencyYes
collateral_coinYes
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided. The description only mentions the action and parameters, but does not disclose effects like whether the loan is fully or partially repaid, fees, minimum amounts, success/failure conditions, or any state changes. For a repayment tool, this is insufficient behavioral context.

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 with two sentences and a bullet list. The purpose is front-loaded. While concise, it could include more structural information without becoming verbose, such as usage hints or parameter details.

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 large set of sibling tools and lack of output schema, the description is too minimal. It does not explain the impact on the loan (e.g., is this a partial or full repayment, how collateral is affected), preconditions, or typical use cases. It leaves the agent with incomplete understanding.

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

Parameters1/5

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

The description merely repeats parameter names with one-word definitions (e.g., 'Loan currency.'), adding no meaning beyond the schema field titles. With 0% schema description coverage, the description fails to provide format constraints, examples, or relationships. This is barely an improvement over the schema alone.

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 (repay) and resource (flexible crypto loan with collateral). However, it does not differentiate from sibling tools like new_crypto_loan_flexible_repay or new_crypto_loan_fixed_repay_collateral, which have similar names and purposes.

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 on when to use this tool versus alternatives. For example, it does not explain when to use this instead of new_crypto_loan_flexible_repay (which might be without collateral) or other repayment tools. The description lacks any when-to-use or when-not-to-use 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