Skip to main content
Glama
longbridge

longbridge

Official

Order Detail

order_detail
Read-onlyIdempotent

Fetch detailed order information by order ID: status, price, execution quantities, and timestamps. Input the order ID from submitted or historical orders.

Instructions

Get detailed information about a specific order. Returns {order_id, symbol, status, side, order_type, quantity, price, executed_quantity, executed_price, submitted_at, time_in_force, msg}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID (returned by submit_order or listed in today_orders / history_orders)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID.
statusYesStatus enum (e.g. `Filled`, `WaitToNew`, `Canceled`).
symbolYesSecurity symbol, e.g. "700.HK".
stock_nameYesDisplay name of the security.
quantityYesSubmitted quantity.
executed_quantityYesQuantity already executed.
priceNoSubmitted limit price (null for market orders).
executed_priceNoVolume-weighted average executed price (null when unfilled).
submitted_atYesOrder submission time (RFC3339).
sideYesBuy or Sell.
order_typeYesOrder type enum, e.g. `LO`, `MO`, `LIT`.
last_doneNoLatest price snapshot at order time (null if missing).
trigger_priceNoTrigger price for LIT/MIT/trailing orders.
msgYesReject message or remark.
tagYesOrder tag (e.g. `Normal`, `LongTerm`).
time_in_forceYesTime-in-force: `Day` / `GTC` / `GTD`.
expire_dateNoGTD expiry date (yyyy-mm-dd).
updated_atNoLast update time (RFC3339).
trigger_atNoConditional-order trigger time (RFC3339).
trailing_amountNoTrailing-stop trail amount (TSLPAMT).
trailing_percentNoTrailing-stop trail percent (TSLPPCT, decimal).
limit_offsetNoTrailing-stop limit offset (TSLPAMT/TSLPPCT).
trigger_statusNoTrigger status, e.g. `Deactive` / `Active` / `Released`.
currencyYesSettlement currency.
outside_rthNoOutside-RTH setting: `RTH_ONLY` / `ANY_TIME` / `OVERNIGHT`.
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds value by specifying the exact set of fields returned, which goes beyond the annotation-provided safety profile.

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?

The description is two sentences: the first states the purpose, the second lists the return fields. It is concise, efficient, and front-loaded with essential information.

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 the single parameter and the presence of an output schema (implied by the description listing fields), the description provides complete context for a simple detail retrieval tool.

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% and the schema already describes the parameter's purpose (returned by submit_order or listed in today_orders/history_orders). The tool description does not add additional semantics, so baseline 3 is appropriate.

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 'Get detailed information about a specific order' and enumerates the returned fields, which distinguishes it from sibling tools like 'today_orders' that list orders rather than provide details for a single 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 implicitly suggests using this tool after obtaining an order_id from 'submit_order', 'today_orders', or 'history_orders' (via the schema description), but it does not explicitly state when to use this tool versus alternatives or provide any exclusion conditions.

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