Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

createTwapStrategy

Executes large orders by splitting them into smaller trades at regular intervals to reduce market impact and achieve an average price over a specified duration.

Instructions

Creates a TWAP strategy that splits a large order into smaller chunks and executes them evenly over a specified time period to minimize market impact.

When to use:

  • You need to execute a large order without moving the market significantly

  • You want to achieve an average price over a specific time window

  • You need to avoid detection by splitting orders over time

Execution behavior:

  1. Total size is divided by (duration / interval) to calculate each order size

  2. Orders are placed at regular intervals (or randomized if isRandom=true)

  3. Each order can be market or limit order based on chase parameters

  4. Strategy stops when duration expires or size is fully executed

Important notes:

  • Minimum recommended duration: 300 seconds (5 minutes) for limit orders

  • Set maxChasePrice or triggerPrice for price protection

  • Enable isRandom to prevent strategy pattern detection

  • Rate limit: 10 requests per second per UID

Agent hint: Use this endpoint when user wants to execute a large order over time to reduce market impact. This is ideal for "buy 10 BTC over the next 5 minutes" type requests. Do not use if user wants immediate execution - use regular order creation instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
symbolYes
sideYes
sizeYes
strategyTypeNotwap
durationYes
intervalNo
isRandomNo
triggerPriceNo
maxChasePriceNo
chaseDistanceNo
chasePercentE4No
reduceOnlyNo
positionIdxNo0
leverageTypeNo0
Behavior5/5

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

With no annotations provided, the description carries full burden and delivers: execution steps (size division, intervals, order types), important notes (minimum 300s duration, price protection, randomization), and rate limit (10 req/s). This fully informs the agent of the tool's behavior and constraints.

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?

Well-structured with markdown headers (When to use, Execution behavior, Important notes, Agent hint), bullet points, and bold emphasis. Every sentence adds value. Front-loaded with purpose. Appropriate length for a complex strategy tool.

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, 0% schema coverage, and no output schema, the description covers purpose, usage, behavior, and important constraints comprehensively. However, it does not describe the return value (e.g., strategy ID), which would help the agent handle the response. Missing explanation for required parameters beyond duration is a minor gap.

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%, so the description must explain parameters. It covers TWAP-specific ones (duration, interval, isRandom, chase parameters, triggerPrice) but omits common ones like category, symbol, side, size, reduceOnly, positionIdx, leverageType. These are not defined in schema either, leaving the agent to infer or guess. Explanation of size, side, etc., would have made it complete.

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 the tool creates a TWAP strategy to split large orders into smaller chunks over time, minimizing market impact. It distinguishes itself from sibling tools like createOrder (immediate execution) and other strategy tools (iceberg, DCA) by focusing on time-weighted average price execution.

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' and 'Do not use' conditions, including examples like 'buy 10 BTC over the next 5 minutes'. The 'Agent hint' section clarifies this is not for immediate execution, directing to regular order creation instead. No other sibling tool description offers such clear usage boundaries.

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