Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

queryStrategyOrderList

Retrieve detailed execution info for all child orders created by a specific trading strategy. Use to monitor order status, analyze fill prices, or debug strategy failures.

Instructions

Retrieve a list of child orders created by a strategy with detailed execution information.

When to use:

  • View all orders spawned by a specific strategy

  • Check why a strategy order was rejected or canceled

  • Analyze execution prices and timing of strategy orders

  • Monitor real-time order status during strategy execution

  • Debug strategy execution issues

Order Status Values:

  • 1: Created - Order placed but not yet filled

  • 2: PartiallyFilled - Order partially executed

  • 3: Filled - Order fully executed

  • 4: Cancelled - Order was canceled

  • 5: Rejected - Order rejected by exchange

Important notes:

  • strategyId is REQUIRED - must provide the parent strategy ID

  • Orders are sorted by creation time (newest first)

  • Use pagination for strategies with many orders

  • Maximum pageSize: 50, default: 20

  • Error codes in response indicate order rejection reasons

  • parentOrderId links replacement orders in chase strategies

Agent hint: Use this endpoint when user wants to see individual orders created by a strategy. Common queries: "show me the orders for strategy X", "why did my TWAP fail", "what prices did my iceberg orders fill at". Requires strategyId - if user doesn't provide it, ask them or query strategy list first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategyIdYes
statusNo
symbolNo
BeginTimeE0No
EndTimeE0No
pageSizeNo
cursorNo
StrategyTypeNo
Behavior4/5

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

No annotations provided, so the description carries full burden. It details sorting order (newest first), pagination limits (max 50, default 20), status meanings and error codes, and the role of parentOrderId. Lacks rate limits or data freshness, but comprehensive overall.

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 headings and bullet points. Efficient overall, though the agent hint partly repeats the 'When to use' section. Each part serves a purpose, and the length is appropriate for the complexity.

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?

Given no output schema and 8 parameters, the description covers purpose, usage, pagination, and statuses. However, missing parameter descriptions for over half the parameters and no indication of response shape leaves gaps. Adequate but not exhaustive.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It explains the status enum values fully and notes strategyId is required, but leaves other parameters (symbol, BeginTimeE0, EndTimeE0, cursor, StrategyType) completely undescribed. Incomplete compensation for missing schema docs.

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 'Retrieve a list of child orders created by a strategy with detailed execution information.' The verb 'retrieve' and specific resource 'child orders of a strategy' clearly differentiate it from sibling tools like getOrderList or getOpenOrders.

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?

Includes a dedicated 'When to use' section with specific scenarios (view orders, check rejections, analyze prices, monitor real-time, debug) and an agent hint on requiring strategyId, plus guidance to ask for it if missing. Provides explicit context and 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