Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_crypto_loan_adjustment_history

Retrieve the history of loan-to-value (LTV) adjustments for crypto loans, with optional filtering by collateral currency and limit on number of records.

Instructions

Get crypto loan LTV adjustment history.

Args: collateral_currency: Filter by collateral currency (optional). limit: Number of records (default: 50).

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

Input Schema

NameRequiredDescriptionDefault
collateral_currencyNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it's a read operation (get history) and mentions default limit. It does not discuss pagination, ordering, rate limits, or whether it's safe (non-destructive). This is insufficient for full transparency.

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 and to the point, with an args listing. It avoids unnecessary words but sacrifices completeness.

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, the description should elaborate on what the history contains (e.g., timestamps, LTV changes). It does not explain the response structure, ordering, or edge cases like empty history. The tool is simple but the description lacks essential context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description adds value by explaining both parameters ('filter by collateral currency' and 'number of records with default 50'). However, it lacks format details (e.g., currency code ISO) and does not cover all potential values.

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 it retrieves crypto loan LTV adjustment history, distinguishing it from mutation tools like crypto_loan_adjust_ltv. However, it does not differentiate from the similar sibling get_new_crypto_loan_adjustment_history, which may cause confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions optional filters but provides no guidance on when to use this tool vs. alternatives. No explicit when-not or comparison with similar history 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