Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

amend_order

Modify an open order's quantity or price on Bybit. Provide symbol and order ID, optionally update qty or price.

Instructions

Amend (modify) an existing open order.

Args: symbol: The trading pair, e.g., BTCUSDT. order_id: Order ID to amend. category: Product type: spot, linear, inverse (default: spot). qty: New quantity (optional, leave empty to keep unchanged). price: New price (optional, leave empty to keep unchanged).

Returns: Amendment result.

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": {
      "symbol": "<symbol>",
      "order_id": "<order_id>"
    },
    "name": "amend_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
order_idYes
categoryNospot
qtyNo
priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behaviors. It only mentions modifying an existing open order and returns an amendment result, omitting important traits like state prerequisites, side effects, or error conditions.

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 structured with Args and Returns sections, making it easy to scan. It is clear but could be slightly more concise.

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?

The description covers parameter details and return type, but lacks information on constraints (e.g., order state), error handling, and behavioral nuances, leaving gaps given the absence of annotations and output schema.

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?

Input schema has 0% coverage, but the description explains each parameter's purpose, including optionality and defaults (e.g., 'qty: New quantity (optional, leave empty to keep unchanged)'), significantly adding value.

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's purpose: 'Amend (modify) an existing open order.' It uses a specific verb and resource, distinguishing it from siblings like cancel_order or place_order.

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 implies usage for modifying a single open order but does not explicitly contrast with alternatives like batch_amend_order or amend_spread_order, nor does it state when not to use it.

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