Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

postCryptoLoanFixedRepayCollateral

Repay a fixed-term crypto loan by converting collateral to loan currency. Input loan ID, loan currency, collateral coin, and amount.

Instructions

Repay loan by converting collateral to loan currency.

Rate limit: 1 request per UID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loanIdYes
loanCurrencyYes
collateralCoinYes
amountYes
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only mentions a rate limit (1 request per UID), but omits side effects, permissions, reversibility, or the impact on loan status. For a mutation tool, this is insufficient.

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 two sentences, which is concise, but it is under-specified for a 4-parameter tool. It is not verbose, but lacks necessary detail.

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 complexity (4 required parameters, no output schema, many siblings), the description fails to explain parameters, differentiate from similar tools, or disclose behavioral aspects beyond rate limit. It is incomplete.

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%, and the description provides no explanation of the 4 required parameters (loanId, loanCurrency, collateralCoin, amount). The agent has no additional meaning beyond the schema.

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 'Repay loan by converting collateral to loan currency' which is a specific verb and resource, but it does not explicitly differentiate from sibling tools like postCryptoLoanFixedFullyRepay or postCryptoLoanFlexibleRepay, leaving ambiguity about the fixed vs flexible context.

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 vs alternatives. With many sibling repay tools, the description should provide context on when converting collateral is appropriate, but it offers none.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bybit-exchange/trading-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server