Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

queryBorrowLiability

Read-only

Retrieve a coin's borrow liability breakdown, splitting fixed-rate, flexible-rate, spot, and derivatives amounts. Designed for unified accounts.

Instructions

Query the borrow liability breakdown for a specific coin, including fixed-rate and flexible-rate liabilities.

Rules:

  • Returns total, fixed-rate, flexible-rate, spot, and derivatives borrow amounts

  • currency is required

  • Data is aggregated from Asset wallet and UTA user positions

  • Unified account only

Service: bizasset-uta-loan-prod

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "currency": "<currency>"
    },
    "name": "queryBorrowLiability"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context by specifying the exact return components and the data sources. This goes beyond the annotation and helps an agent understand what the tool actually exposes.

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 compact and front-loaded with the core purpose, followed by useful rules and service context. The line about 'currency' being required is redundant with the schema, but it does not add meaningful bloat.

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 one-parameter read-only tool with no output schema, the description covers the essential invocation context: what is returned, what input is needed, and which account type applies. It does not describe response structure in detail, but the listed return categories are sufficient for basic usage.

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 carries the burden. It clarifies that 'currency' refers to the specific coin, but it does not provide format, examples, or accepted currency codes. Minimal but adequate for a single obvious 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 description uses a specific verb ('Query') and a specific resource ('borrow liability breakdown for a specific coin'), and lists the exact returned components. This clearly differentiates it from nearby siblings like getBorrowHistory or accountBorrow.

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?

The description gives a clear usage context: it is for unified accounts only and aggregates from Asset wallet and UTA positions. It does not explicitly name alternatives or say when not to use it, but the unified-account restriction is an explicit exclusion.

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