longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

Order Detail

order_detail

Read-onlyIdempotent

Get full details for a specific order by providing its order ID. Use this to check status, fills, and execution information from your order history.

Instructions

Get detailed information about a specific order.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	Order ID (from today's orders or order history)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`msg`	No
`tag`	No
`side`	No
`order`	No
`price`	No
`status`	No
`symbol`	No
`currency`	No
`order_id`	No
`quantity`	No
`last_done`	No
`order_type`	No
`stock_name`	No
`trigger_at`	No
`updated_at`	No
`expire_date`	No
`outside_rth`	No
`limit_offset`	No
`submitted_at`	No
`time_in_force`	No
`trigger_price`	No
`executed_price`	No
`trigger_status`	No
`trailing_amount`	No
`trailing_percent`	No
`executed_quantity`	No
`current_millisecond`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv0.8.7Aug 19, 2026

changedInput schema / properties / order_id / description

Previous value: -"Order ID (returned by submit_order or listed in today_orders / history_orders)"New value: +"Order ID (from today's orders or order history)"

Changed17 schema fields changedv0.8.4Jul 25, 2026

addedOutput schema / $defs

Added value: +{
+  "UsOrderDetail": {
+    "properties": {
+      "action": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "currency": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "done_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "executed_amount": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "executed_price": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "executed_qty": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "operate_direction": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "order_histories": {
+        "items": {
+          "$ref": "#/$defs/UsOrderHistoryEntry"
+        },
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "order_type": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "price": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "quantity": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "security_type": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "status": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "submitted_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "symbol": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "time_in_force": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "UsOrderHistoryEntry": {
+    "properties": {
+      "occurred_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "price": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "qty": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "status": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

changedOutput schema / properties / currency / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / current_millisecond

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / executed_quantity / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / msg / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / order

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/UsOrderDetail"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / order_id / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / order_type / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / quantity / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / side / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / status / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / stock_name / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / submitted_at / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / symbol / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / tag / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / time_in_force / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedOutput schema / required

Removed value: -[
-  "order_id",
-  "status",
-  "symbol",
-  "stock_name",
-  "quantity",
-  "executed_quantity",
-  "submitted_at",
-  "side",
-  "order_type",
-  "msg",
-  "tag",
-  "time_in_force",
-  "currency"
-]

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"OrderIdParam"
```

Changed28 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed value: -"Returned by `order_detail`. Single order with full lifecycle metadata."

removedOutput schema / properties / currency / description
```
Removed value: -"Settlement currency."
```

removedOutput schema / properties / executed_price / description

Removed value: -"Volume-weighted average executed price (null when unfilled)."

removedOutput schema / properties / executed_quantity / description
```
Removed value: -"Quantity already executed."
```
removedOutput schema / properties / expire_date / description
```
Removed value: -"GTD expiry date (yyyy-mm-dd)."
```

removedOutput schema / properties / last_done / description

Removed value: -"Latest price snapshot at order time (null if missing)."

removedOutput schema / properties / limit_offset / description

Removed value: -"Trailing-stop limit offset (TSLPAMT/TSLPPCT)."

removedOutput schema / properties / msg / description
```
Removed value: -"Reject message or remark."
```
removedOutput schema / properties / order_id / description
```
Removed value: -"Order ID."
```

removedOutput schema / properties / order_type / description

Removed value: -"Order type enum, e.g. `LO`, `MO`, `LIT`."

removedOutput schema / properties / outside_rth / description

Removed value: -"Outside-RTH setting: `RTH_ONLY` / `ANY_TIME` / `OVERNIGHT`."

removedOutput schema / properties / price / description

Removed value: -"Submitted limit price (null for market orders)."

removedOutput schema / properties / quantity / description
```
Removed value: -"Submitted quantity."
```
removedOutput schema / properties / side / description
```
Removed value: -"Buy or Sell."
```

removedOutput schema / properties / status / description

Removed value: -"Status enum (e.g. `Filled`, `WaitToNew`, `Canceled`)."

removedOutput schema / properties / stock_name / description
```
Removed value: -"Display name of the security."
```
removedOutput schema / properties / submitted_at / description
```
Removed value: -"Order submission time (RFC3339)."
```
removedOutput schema / properties / symbol / description
```
Removed value: -"Security symbol, e.g. \"700.HK\"."
```

removedOutput schema / properties / tag / description

Removed value: -"Order tag (e.g. `Normal`, `LongTerm`)."

removedOutput schema / properties / time_in_force / description
```
Removed value: -"Time-in-force: `Day` / `GTC` / `GTD`."
```
removedOutput schema / properties / trailing_amount / description
```
Removed value: -"Trailing-stop trail amount (TSLPAMT)."
```

removedOutput schema / properties / trailing_percent / description

Removed value: -"Trailing-stop trail percent (TSLPPCT, decimal)."

removedOutput schema / properties / trigger_at / description

Removed value: -"Conditional-order trigger time (RFC3339)."

removedOutput schema / properties / trigger_price / description

Removed value: -"Trigger price for LIT/MIT/trailing orders."

removedOutput schema / properties / trigger_status / description

Removed value: -"Trigger status, e.g. `Deactive` / `Active` / `Released`."

removedOutput schema / properties / updated_at / description
```
Removed value: -"Last update time (RFC3339)."
```
removedOutput schema / title
```
Removed value: -"OrderDetailResponse"
```

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the basic read operation, but it does not contradict 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.

Conciseness5/5

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

The description is a single clear sentence with no wasted words. It is appropriately sized for a simple read-only lookup tool.

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 the tool's low complexity, one well-documented parameter, strong annotations, and an output schema, the description is nearly complete. It could be slightly improved by noting the source of order IDs or distinguishing from IPO order details, but it is sufficient for basic invocation.

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% and the single order_id parameter is already described as coming from today's orders or order history. The description adds no additional parameter meaning beyond what the schema provides.

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

Purpose4/5

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

The description clearly states the tool's function: retrieving detailed information about a specific order. It is distinct from list-oriented tools like today_orders and history_orders, though it does not explicitly differentiate itself from ipo_order_detail or other order-related tools.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that the order_id must come from today's orders or order history, nor does it contrast with sibling tools like today_orders, history_orders, or ipo_order_detail.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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