Skip to main content
Glama
longbridge

longbridge

Official

Replace Order

replace_order
DestructiveIdempotent

Modify an open order's quantity, price, trigger price, or trailing parameters. Only pending orders can be updated.

Instructions

Modify an open order's quantity, price, trigger_price, or trailing params. Returns "order replaced" on success. Only open/pending orders can be modified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID to replace (returned by submit_order or listed in today_orders / history_orders)
quantityYesNew order quantity (number of shares)
priceNoNew limit price (for limit-style orders)
trigger_priceNoNew trigger (activation) price (for LIT / MIT / trailing-stop orders)
limit_offsetNoNew limit offset from the trailing stop price (for TSLPAMT / TSLPPCT)
trailing_amountNoNew trailing amount as absolute price distance (for TSLPAMT)
trailing_percentNoNew trailing percent as decimal e.g. 0.05 = 5% (for TSLPPCT)
Behavior5/5

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

The description adds value beyond annotations by stating the return value 'order replaced' on success and reinforcing the precondition. Annotations already indicate destructive and idempotent, but the description provides concrete behavioral info.

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?

Two sentences efficiently convey purpose, scope, and return value with no superfluous words. Well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately covers the return value and precondition. The 7 parameters are well-documented in the schema, so the description is sufficient for contextual completeness.

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 100%, so baseline is 3. The description briefly lists parameter categories but adds minimal insight beyond the schema's detailed descriptions.

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 modifies open orders, listing the specific parameters that can be changed (quantity, price, trigger_price, trailing params). It differentiates from siblings like submit_order and cancel_order by focusing on modification of existing orders.

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

Usage Guidelines4/5

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

The description explicitly states that only open/pending orders can be modified, providing a condition for use. However, it does not explicitly contrast with alternatives like cancel+resubmit, but the sibling list implies context.

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/longbridge/longbridge-mcp'

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