Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getCryptoLoanFixedBorrowOrderQuote

Read-only

Compare fixed-term crypto lending offers by retrieving current borrow quotes from market supply orders, enabling informed decisions before submitting a loan request.

Instructions

Query available supply orders (lending offers) from the market for a specific currency and term.

Features:

  • Public endpoint (no authentication required)

  • View available lending offers before placing borrow order

  • Sort by rate or amount

  • Filter by currency and term

  • Rate limit: 1000 requests per time window

Use Cases:

  • Check available rates before borrowing

  • Find best lending offers in the market

  • Compare rates across different terms

Important:

  • Results show actual supply orders from lenders

  • Rates may change as orders are filled

  • Use these rates when creating borrow orders

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

Input Schema

NameRequiredDescriptionDefault
sortNo
termNo
limitNo
orderByNo
orderCurrencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A4.3/5.0
Behavior5/5

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

The description adds meaningful behavior beyond readOnlyHint/openWorldHint: public endpoint with no authentication, rate limit of 1000 requests per window, and caveat that rates may change as orders fill. This lets an agent anticipate side effects and volatility.

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 first sentence is a clear front-loaded summary and the bold section labels make it skimmable. Some redundancy exists between the Features and Use Cases bullets, but the content is not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only quote endpoint with no required parameters and no output schema, the description covers authentication, rate limiting, market behavior, and intended usage. The only notable gap is the undocumented semantics of the sort enum values.

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?

With 0% schema description coverage, the description partially compensates by saying the tool filters by currency and term and sorts by rate or amount, which maps to orderCurrency/term and orderBy. However, it does not explain the meaning of the sort enum values ('1'/'2'), the term format, or the limit parameter.

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 first sentence states a specific action and resource: query available supply orders/lending offers from the market for a currency and term. It also clarifies the operational context ('before placing borrow order'), which distinguishes it from supply-side order info/quote siblings.

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

Usage Guidelines4/5

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

Explicit Use Cases (check rates before borrowing, find best offers, compare terms) and the note 'Use these rates when creating borrow orders' give clear context. It does not name alternative tools or state when not to use it, so it stops short of full exclusion guidance.

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