Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

otc_loan_repay

Repay an OTC loan by specifying the token and repayment amount.

Instructions

Repay OTC loan.

Args: token: Repay token/coin. quantity: 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": {
      "token": "<token>",
      "quantity": "<quantity>"
    },
    "name": "otc_loan_repay"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as whether it is a mutation, required permissions, potential side effects, or constraints. This is insufficient for a write operation.

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 (two sentences for parameters) and front-loaded with the main action. However, the parameter explanations could be integrated more concisely without adding length.

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 low schema coverage, the description lacks completeness. It does not specify return values, prerequisites, or how OTC loans differ from other loans, leaving significant gaps for an agent to act correctly.

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%, so the description must add meaning. It briefly explains token as 'Repay token/coin' and quantity as 'Repay amount', which adds marginal value over parameter names but does not provide detailed formats or constraints.

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 'Repay OTC loan' clearly states the action and resource, but does not differentiate from sibling tools like 'crypto_loan_repay' or 'new_crypto_loan_fixed_repay', which reduces clarity.

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 other loan repay tools. Many sibling tools exist with similar purposes (e.g., crypto_loan_repay, manual_repay), and the description provides no context for selection.

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