Skip to main content
Glama
longbridge

longbridge

Official

Submit Order

submit_order
Destructive

Submit buy and sell orders for HK and US markets with support for multiple order types, price conditions, and time-in-force options.

Instructions

Submit a buy/sell order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYesBuy or Sell
remarkNoOrder remark (max 255 characters)
symbolYesSecurity symbol, e.g. "700.HK"
order_typeYesOrder type (HK supports all; US supports LO/MO/LIT/MIT/TSLPAMT/TSLPPCT only): - LO (Limit Order): requires submitted_price - ELO (Enhanced Limit Order, HK only): requires submitted_price - MO (Market Order): no price required - AO (At-auction Order, HK only): executed at auction price, no price required - ALO (At-auction Limit Order, HK only): requires submitted_price - ODD (Odd Lots Order, HK only): requires submitted_price, for non-standard lot sizes - LIT (Limit If Touched): requires submitted_price and trigger_price; activates when market price touches trigger_price - MIT (Market If Touched): requires trigger_price only; executes at market when trigger_price is touched - TSLPAMT (Trailing Limit If Touched by Amount): requires trailing_amount and limit_offset; trailing stop by fixed amount - TSLPPCT (Trailing Limit If Touched by Percent): requires trailing_percent (0-1) and limit_offset; trailing stop by percentage - SLO (Special Limit Order, HK only): requires submitted_price; cannot be replaced after submission
expire_dateNoExpiry date (yyyy-mm-dd). Required when time_in_force is GTD
outside_rthNoOutside regular trading hours: "RTH_ONLY" (regular trading hours only), "ANY_TIME" (any time including pre/post market), "OVERNIGHT" (overnight session, US only)
limit_offsetNoLimit offset from the trailing stop price. Required for: TSLPAMT, TSLPPCT
time_in_forceYesOrder validity: "Day" (Day Order, expires end of session), "GTC" (Good Til Canceled), "GTD" (Good Til Date, requires expire_date)
trigger_priceNoTrigger (activation) price. Required for: LIT, MIT, TSLPAMT, TSLPPCT
submitted_priceNoLimit price. Required for: LO, ELO, ALO, ODD, LIT, SLO
trailing_amountNoTrailing amount (absolute price distance). Required for TSLPAMT
trailing_percentNoTrailing percent as decimal (e.g. 0.05 = 5%). Required for TSLPPCT
submitted_quantityYesOrder quantity (number of shares)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes
Behavior2/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) with destructive potential (destructiveHint=true). The description adds no additional behavioral disclosure, such as that orders are submitted asynchronously, may be rejected, or that certain parameter combinations are invalid. This is insufficient given the tool's financial impact.

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

Conciseness3/5

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

The description is very concise at one sentence, but it is too terse for a tool with 13 parameters and significant complexity. While front-loaded, it sacrifices valuable context that could be provided in a few more sentences. It earns its place but could be more informative without verbosity.

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?

Given the rich input schema (100% coverage) and the presence of an output schema, the description's burden is reduced. However, it omits critical context like the fact that submission depends on account status, market hours, and order type validity. The description is minimally adequate but not complete for a complex trading action.

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?

All 13 parameters have full descriptions in the input schema (100% coverage), so the description does not need to elaborate on them. The description 'buy/sell order' confirms the side parameter but adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 'Submit a buy/sell order' clearly identifies the verb (submit) and resource (order), and it specifies the two possible sides (buy/sell). This distinguishes it from sibling tools like cancel_order and replace_order. However, it could be more specific about the context (e.g., securities trading) and omit 'buy/sell' redundantly with the schema's side parameter.

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 like cancel_order, replace_order, or order_detail. There is no mention of prerequisites, market hours, or conditions under which submission might fail. Without such context, agents may misuse it.

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