Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

place_limit_order

Place a limit order to buy or sell a trading pair at a specified price on Bybit.

Instructions

Place a limit order to buy or sell.

Args: symbol: The trading pair, e.g., BTCUSDT. side: Buy or Sell. qty: Amount to trade. price: Limit price. category: Product type: spot, linear, inverse (default: spot).

Returns: Order placement result.

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": {
      "symbol": "<symbol>",
      "side": "<side>",
      "qty": "<qty>",
      "price": "<price>"
    },
    "name": "place_limit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
sideYes
qtyYes
priceYes
categoryNospot

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 must fully disclose behavior. It mentions placing an order but does not state order validity (e.g., GTC, IOC), execution behavior, fees, or cancellation rules. For a trading tool, this is insufficient.

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 short and structured with an Args section. However, the Returns section is vague ('Order placement result') and could be more concise by merging or removing it. Still, it is not overly long.

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 no output schema and no annotations, the description is too minimal. It does not explain return values, order types, time-in-force, or special conditions. For a limit order tool, more detail is needed.

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%, but the description adds meaning for all 5 parameters: symbol, side, qty, price, and category (with default and product types). This adds value beyond the schema titles, but does not explain formats or constraints.

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 clearly states it places a limit order to buy or sell, specifies the trading pair, side, quantity, limit price, and category. It distinguishes itself from siblings like 'place_market_order' by explicitly naming 'limit order'.

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 a limit order versus other order types (e.g., market order), no prerequisites, no context for choosing category or time-in-force. The description lacks any usage recommendations.

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