Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

new_crypto_loan_fixed_repay

Repay a fixed crypto loan in full. Provide either the loan ID or the loan currency.

Instructions

Fully repay a fixed crypto loan.

Args: loan_id: Loan ID (either loan_id or loan_currency required). loan_currency: Loan currency.

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

Input Schema

NameRequiredDescriptionDefault
loan_idNo
loan_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/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 only states 'Fully repay a fixed crypto loan,' which is minimal and does not disclose behavioral traits like safety, permissions, or consequences beyond being a repayment action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with one sentence and an Args list, but it is too minimal. It could be improved with clearer structure and relevant 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 no annotations, no output schema, and low schema coverage, the description is incomplete. It does not explain return values, error handling, or behavioral context, leaving the agent underinformed.

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?

Schema description coverage is 0%, so the description must compensate. It states 'either loan_id or loan_currency required,' but the schema shows both parameters with default '' and no required constraint, contradicting the schema. This misleads the agent.

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 'Fully repay a fixed crypto loan,' which is a specific verb and resource. However, it does not differentiate from sibling tools like new_crypto_loan_fixed_repay_collateral or new_crypto_loan_flexible_repay.

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 input guidance (loan_id or loan_currency required) but lacks any when-to-use vs alternatives or when-not-to-use guidance. No explicit context for use.

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