Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

batch_place_order

Simplify order management by submitting up to 10 orders in a single API call. Supports various product types for efficient bulk trading.

Instructions

Place multiple orders in a single request (max 10).

Args: category: Product type: spot, linear, inverse, option. orders: List of order dicts. Each must contain: symbol, side, orderType, qty. Optional fields: price, timeInForce, orderLinkId, etc. Example: [{"symbol": "BTCUSDT", "side": "Buy", "orderType": "Limit", "qty": "0.01", "price": "50000"}]

Returns: Batch order placement results.

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": {
      "category": "<category>",
      "orders": "<orders>"
    },
    "name": "batch_place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes
ordersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations provided; description only mentions max 10 orders but omits side effects, atomicity, error handling, or permission requirements for a mutation tool.

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, structured with Args and Returns, includes an example; no unnecessary words.

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

Completeness3/5

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

Lacks detail on return structure (just 'batch order placement results') and does not address potential partial failures or result format; incomplete for a batch operation 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?

Schema coverage is 0%; description adds significant value by specifying category options and required fields for each order dict, plus an example, far exceeding the schema's generic types.

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 'Place multiple orders in a single request (max 10)', which is a specific verb and resource, and distinguishes from single-order siblings like place_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 Guidelines4/5

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

Implies usage for batch vs single orders, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like place_market_order.

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