Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

repay_liability

Repay liabilities on Bybit. Specify a coin to repay a specific liability, or leave empty to repay all.

Instructions

Quick repay liability.

Args: coin: Coin with liability (optional, repays all if empty).

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

Input Schema

NameRequiredDescriptionDefault
coinNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes the action as 'quick repay' but does not disclose behavioral traits such as whether it is atomic, checks balances, handles partial repayment, or returns status. The description is too sparse for a mutation 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 lines) and front-loaded with a clear purpose. Every sentence adds value, but it could be slightly expanded with key details without losing conciseness. It is efficient but not fully informative.

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 is a mutation with no output schema and many sibling repayment tools, the description lacks critical context: return values, error conditions, prerequisites, and differentiation. It is not complete enough for safe and correct usage without external knowledge.

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 input schema has 0% description coverage, providing only a title. The description adds meaning: 'coin: Coin with liability (optional, repays all if empty).' This explains the parameter's behavior beyond the schema, clarifying optionality and default action. For a single parameter, this is sufficient value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'repay' and resource 'liability', making the core action clear. However, it does not distinguish this tool from similar sibling tools like crypto_loan_repay or manual_repay, and the term 'quick' is vague. Scope (which liability type) is unspecified.

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?

The description provides a condition for the parameter (coin empty repays all) but offers no guidance on when to use this tool versus alternatives, no prerequisites, no when-not scenarios, and no examples. It fails to help an agent choose among repayment 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