Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getSpotBorrowQuota

Query the spot margin borrowing quota to return max tradeable quantity with and without borrowing, and identify borrowable coins before placing an order.

Instructions

Query the borrowing quota for spot margin trading.

  • Returns max tradeable quantity/amount with and without borrowing

  • Indicates which coin can be borrowed

  • Only applicable to spot category

Agent hint: Use this endpoint to check how much you can trade (including borrowable amount) before placing a spot margin order. TradFi: applies to xStock tokens only (category=spot). Not applicable to equity or commodity perpetuals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
symbolYes
sideYes
Behavior4/5

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

Despite no annotations, description discloses key behavioral traits: returns two types of amounts (with/without borrowing), indicates borrowable coin, and states applicability. Clearly communicates read-only nature implicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise three-part structure: main line, bullet points of key returns, agent hint and TradFi note. Each sentence adds value, no redundancy. Front-loaded with primary purpose.

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 simple query tool with 3 parameters and no output schema, description covers purpose, return content, usage context, and constraints. Lacks explicit return format or edge cases but sufficient for selection.

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 must compensate. It adds meaning for symbol via 'applies to xStock tokens only', but for category it only repeats schema enum ('spot'), and side is unaddressed. Partial compensation.

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?

Clear verb 'Query' and specific resource 'borrowing quota for spot margin trading'. Description details returns (max tradeable quantity/amount with/without borrowing, which coin can be borrowed) and explicitly limits to spot category, distinguishing from sibling tools.

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?

Agent hint explicitly states when to use: 'check how much you can trade before placing a spot margin order'. Also notes non-applicability to equity/commodity perpetuals, providing clear context but no named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bybit-exchange/trading-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server