Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

set_trading_stop

Destructive

Set take profit, stop loss, or trailing stop for a trading position on Bybit. Manage risk by defining exit conditions with price types and order sizes.

Instructions

Set take profit, stop loss, or trailing stop for a position (MEDIUM risk).

    Args:
        category: Product type - linear, inverse
        symbol: Symbol name
        takeProfit: Take profit price
        stopLoss: Stop loss price
        trailingStop: Trailing stop distance
        tpTriggerBy: TP trigger price type - LastPrice, MarkPrice, IndexPrice
        slTriggerBy: SL trigger price type
        tpSize: TP order quantity
        slSize: SL order quantity
        positionIdx: Position index (0: one-way, 1: hedge buy, 2: hedge sell)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slSizeNo
symbolYes
tpSizeNo
categoryYes
stopLossNo
takeProfitNo
positionIdxNo
slTriggerByNo
tpTriggerByNo
trailingStopNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the mutation behavior is known. The description adds 'MEDIUM risk' but no additional behavioral details like side effects or prerequisites.

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?

The description is front-loaded with the purpose and uses a structured Args block. It is slightly verbose but every sentence is informative. No redundancy.

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 10 parameters and an output schema exists, the description covers all parameters and the tool's purpose. It lacks explanation of value differences for price trigger types, but is otherwise complete.

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

Parameters5/5

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

Schema has 0% description coverage. The description provides clear meanings for all 10 parameters, including types and examples like 'Product type - linear, inverse' for category, greatly enhancing understanding.

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 sets take profit, stop loss, or trailing stop for a position. It distinguishes from siblings like place_order and set_leverage by focusing on risk management stops.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description mentions 'MEDIUM risk' but does not explicitly guide when to use this tool versus alternatives like place_order or confirm_order. Usage context is implied but not stated.

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/workspace/bybit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server