Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

createIcebergStrategy

Splits a large order into multiple smaller child orders, displaying only one at a time to hide total size and reduce market impact.

Instructions

Creates an Iceberg strategy that splits a large order into multiple smaller child orders, displaying only one at a time to hide trading intent.

When to use:

  • You have a large order and want to hide total size from the market

  • You want to prevent price manipulation based on your order size

  • You need to reduce market impact while maintaining consistent pricing

  • You want to earn maker rebates by using post-only orders

Execution behavior:

  1. Calculate child order size:

    • If subSize provided: orderCount = size / subSize

    • If orderCount provided: subSize = size / orderCount

  2. Create first child order (limit or chase pricing)

  3. Wait for child order to fill completely

  4. Once filled, create next child order

  5. Repeat until all size is executed

  6. Each child order is independent - can have different prices if chasing

Important notes:

  • Recommended subSize: 5%-20% of total size

  • Enable postOnly=1 to get maker fee rebates

  • Set chaseDistance="-1" for aggressive taker execution (hit best bid/ask)

  • Always set maxChasePrice for price protection

  • Strategy executes sequentially - slower than Chase but more stealthy

  • If a child order is partially filled and canceled, strategy continues with remaining amount

Agent hint: Use this endpoint when user wants to hide large order size from the market. Best for "buy 100 BTC without showing the full size" type requests. Do not use for time-sensitive execution - use Chase Order instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
symbolYes
sideYes
sizeYes
strategyTypeNoiceberg
subSizeNo
orderCountNo
limitPriceNo
chaseDistanceNo
chasePercentE4No
maxChasePriceNo
postOnlyNo0
reduceOnlyNo
positionIdxNo0
leverageTypeNo0
Behavior5/5

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

Provides detailed step-by-step execution behavior, including child order calculation, sequential filling, and behavior on partial fills. Covers effect of parameters like postOnly, chaseDistance, and maxChasePrice. No annotations provided, so description carries full burden.

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 clear sections (When to use, Execution behavior, Important notes, Agent hint). Slightly lengthy but every section adds value. Front-loaded with 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?

Given 15 parameters, high complexity, no output schema or annotations, the description is comprehensive. Covers usage, behavior, parameter advice, and trade-offs. Minor lack of return value specification but overall complete.

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?

Adds significant meaning beyond the input schema: explains relationship between subSize and orderCount, recommends subSize range, clarifies use of chaseDistance='-1' for aggressive taker, and importance of maxChasePrice for price protection. Does not cover every parameter (e.g., reduceOnly, positionIdx), but provides value for key parameters.

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 it creates an Iceberg strategy that splits a large order into smaller child orders. Distinct from sibling tools like createChaseOrderStrategy and createTwapStrategy.

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?

Explicitly lists when to use (hide large order, prevent price manipulation, reduce market impact, earn maker rebates) and provides a clear agent hint with when not to use (time-sensitive execution) and alternative (Chase Order).

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