Skip to main content
Glama
longbridge

longbridge

Official

Submit Order

submit_order
Destructive

Place buy/sell orders on HK and US markets using various order types (limit, market, stop, trailing stop) with configurable validity and price triggers.

Instructions

Submit a buy/sell order. order_type: LO (Limit) / ELO (Enhanced Limit, HK) / MO (Market) / AO (At-auction, HK) / ALO (At-auction Limit, HK) / ODD (Odd Lots, HK) / LIT (Limit If Touched) / MIT (Market If Touched) / TSLPAMT (Trailing Limit by Amount) / TSLPPCT (Trailing Limit by Percent) / SLO (Special Limit, HK). side: Buy/Sell. time_in_force: Day/GTC/GTD

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
sideYesBuy or Sell
submitted_quantityYesOrder quantity (number of shares)
time_in_forceYesOrder validity: "Day" (Day Order, expires end of session), "GTC" (Good Til Canceled), "GTD" (Good Til Date, requires expire_date)
submitted_priceNoLimit price. Required for: LO, ELO, ALO, ODD, LIT, SLO
trigger_priceNoTrigger (activation) price. Required for: LIT, MIT, TSLPAMT, TSLPPCT
limit_offsetNoLimit offset from the trailing stop price. Required for: TSLPAMT, TSLPPCT
trailing_amountNoTrailing amount (absolute price distance). Required for TSLPAMT
trailing_percentNoTrailing percent as decimal (e.g. 0.05 = 5%). Required for TSLPPCT
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)
remarkNoOrder remark (max 255 characters)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesThe newly-created order ID. Pass this to `cancel_order` / `replace_order` / `order_detail`.
Behavior3/5

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

Description adds some behavioral context (order type constraints, required fields) beyond annotations which indicate destructive write. However, it does not disclose consequences like order lifecycle, success response, or rate limits.

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 a single dense sentence with many abbreviations and lists. It is not front-loaded and could be better structured for readability, though it contains necessary info.

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 high schema coverage and existence of output schema, the description covers essentials. It omits mention of write nature (covered by annotations) but lacks details on order submission process.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already cover 100% of parameters. The description adds value by summarizing which order types require which fields, reducing cognitive load for the agent.

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?

Description clearly states 'Submit a buy/sell order', specifying the verb and resource. It lists order types, side, and time_in_force, distinguishing it from sibling tools like cancel_order or replace_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?

No explicit guidance on when to use this tool vs alternatives (e.g., replace_order for modifications). Context is implied but not stated, such as prerequisites or scenarios where submission is appropriate.

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