Skip to main content
Glama
longbridge

longbridge

Official

Replace Order

replace_order
DestructiveIdempotent

Replace an existing order by updating quantity, price, trigger price, or trailing stop settings using the original order ID.

Instructions

Replace/modify an existing order

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)
Behavior2/5

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

Annotations already indicate destructive and idempotent behavior. The description adds no further detail about side effects, permissions, or order lifecycle impacts, relying solely on the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one phrase) and lacks necessary detail. It is under-specified rather than optimally concise.

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

Completeness2/5

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

For a 7-parameter tool with conditional fields and no output schema, the description is too sparse. It does not explain how the replacement works, prerequisites, or interactions with other order attributes.

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 description coverage is 100%, with each parameter well-documented in the schema. The description adds no extra meaning beyond what the schema already provides, so baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Replace/modify an existing order,' which identifies the action and resource, but is vague and does not distinguish from sibling tools like cancel_order or submit_order. It could be more specific about what aspects are replaced.

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

Usage Guidelines2/5

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

No guidance on when to use replace_order versus alternatives (e.g., cancel and resubmit, or modify). The description lacks context for proper tool selection.

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