Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getCryptoLoanFixedRepaymentHistory

Read-only

Fetch fixed-term crypto loan repayment history with optional filters for repay ID, loan currency, limit, and cursor.

Instructions

Query loan repayment records.

Rate limit: 5 requests per UID

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
repayIdNo
loanCurrencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description is not responsible for read-safety disclosure. It adds a useful operational constraint, 'Rate limit: 5 requests per UID,' but does not mention pagination, ordering, or data scope.

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 short and front-loaded, with the rate limit presented as a distinct, useful note. It has no filler, though it is sparse enough that it leaves meaningful information gaps.

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?

With no output schema, no parameter descriptions, and no usage context, the description is incomplete for an agent to call the tool correctly. The agent cannot infer repayId semantics, cursor-based pagination behavior, or response shape.

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 does not explain any of the four parameters: limit, cursor, repayId, loanCurrency. With no schema descriptions and no prose compensation, the agent receives no parameter semantics.

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 a specific verb and resource: 'Query loan repayment records.' This is clear, though it does not explicitly differentiate fixed from flexible loan repayment history; the tool name supplies the 'Fixed' qualifier.

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 is provided on when to use this tool versus closely related siblings such as getCryptoLoanFlexibleRepaymentHistory, getBorrowHistory, or accountRepay. The only additional note is a rate limit, which does not help with tool 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