Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_crypto_loan_ongoing_orders

Retrieve your ongoing unpaid crypto loan orders, optionally filtering by loan or collateral currency.

Instructions

Get ongoing (unpaid) crypto loan orders.

Args: loan_currency: Filter by loan currency (optional). 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_ongoing_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_currencyNo
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 bears full burden. It only states 'Get ongoing (unpaid) crypto loan orders' without detailing pagination, sorting, response format, or error handling. The limit parameter implies pagination but is not explained.

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?

Description is brief and front-loaded with purpose. The Args section organizes parameters concisely. No redundant information, but could be slightly more 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 three optional parameters, no output schema, and many sibling loan tools, the description is insufficient. It omits return structure, prerequisites, and how results relate to other loan operations.

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 description adds value by explaining loan_currency and collateral_currency as filters, and limit as number of records with default. However, it lacks details on valid values (e.g., currency codes) and range for limit.

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?

Description clearly states it retrieves 'ongoing (unpaid) crypto loan orders', using a specific verb and resource. This distinguishes it from sibling tools that retrieve historical loan data (e.g., get_crypto_loan_borrow_history, get_crypto_loan_repayment_history).

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 versus alternatives like get_crypto_loan_borrow_history or get_new_crypto_loan_* tools. The description does not specify prerequisites or scenarios where this tool is appropriate.

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