Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getOrderPriceLimit

Check the maximum buy and minimum sell price limits for a symbol to validate your limit order price before placing it and avoid rejection.

Instructions

Retrieve the current allowable price range for order placement, including the maximum buy price limit (buyLmt) and minimum sell price limit (sellLmt).

Use this endpoint when you need to:

  • Validate that a limit order price falls within the allowed range before submission

  • Avoid order rejection due to price-out-of-range errors

  • Check real-time price limits to construct valid orders near the market price

Supported Products: Spot, USDT contract, Inverse contract

Returns buyLmt (maximum allowable bid price) and sellLmt (minimum allowable ask price).

Do not use this endpoint for tick size or price precision — use getInstrumentsInfo instead.

Notes:

  • No authentication required

Agent hint: Use this endpoint to validate that a limit order price is within the allowed range before placing an order. category defaults to linear. symbol is required. Call this before submitting a limit order if you receive price-out-of-range errors. For tick size and price precision constraints, use getInstrumentsInfo instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNolinear
symbolYes
Behavior4/5

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

Discloses read-only nature, no auth required, supported products, and return fields. Lacks details on rate limits or data freshness, but sufficient given no annotations.

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?

Well-structured with bullet points and notes, front-loaded purpose. Slight redundancy between initial list and agent hint, but overall efficient.

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?

Covers return values, supported products, authentication, and use cases. Could add more on error conditions or data freshness, but adequate for a simple retrieval tool.

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

Parameters4/5

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

With 0% schema description coverage, the description adds meaning by specifying default for category and requiring symbol, despite not elongating enum values.

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?

Clearly states the tool retrieves allowable price range for order placement, specifies return fields (buyLmt, sellLmt), and distinguishes from sibling getInstrumentsInfo for tick size/precision.

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

Usage Guidelines5/5

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

Provides explicit when-to-use scenarios (validating limit order price, avoiding rejection) and when-not-to-use (tick size/precision), with alternative named (getInstrumentsInfo). Also notes no authentication required.

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