Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

postCryptoLoanFixedFullyRepay

Repay entire loan principal and interest for a fixed-term crypto loan in a single API call.

Instructions

Repay entire loan principal and interest.

Rate limit: 1 request per UID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loanIdYes
loanCurrencyYes
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It states it repays entire loan principal and interest and includes a rate limit. However, it omits critical details: no mention of authentication requirements, whether the loan is closed after, or any side effects beyond repayment.

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 very short (one sentence plus rate limit), which is concise but under-specified. It wastes no words but fails to provide necessary parameter details or usage context, making it only minimally structured.

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 no annotations, the description is incomplete. It does not describe return values, error conditions, or confirm that the operation is successful. The two-parameter schema is not fully explained, leaving the agent with gaps.

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 input schema has 0% description coverage for parameters. The description adds no meaning to 'loanId' or 'loanCurrency', failing to explain their purpose, format, or how to obtain valid values. This leaves an AI agent guessing.

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

Purpose5/5

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

The description explicitly states 'Repay entire loan principal and interest', which clearly identifies the action and resource. The tool name 'postCryptoLoanFixedFullyRepay' aligns perfectly, and it is distinct from sibling tools like 'postCryptoLoanFixedRepayCollateral' or 'quickRepayment'.

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 gives no guidance on when to use this tool versus alternatives. It does not specify prerequisites (e.g., loan must exist, need to have loanId), nor does it mention scenarios where partial repayment or other repayment methods would be more appropriate.

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