Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Submit Fund Order

fund_submit_order
Destructive

Submit a fund buy/sell order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview to the user, then re-call quoting the code only after they explicitly confirm. Requires auth.

Instructions

Submit a fund buy/sell order. DRY RUN unless execute is the confirmation_code from its own dry run: call once without execute, show the preview to the user, then re-call quoting the code only after they explicitly confirm. Requires auth. counter_id from fund_hot / fund_list; action is buy or sell; currency e.g. HKD/USD; give either amount (cash to invest) or units (shares to sell); is_sell_all=true redeems the whole position. Use fund_validate_order first for a safe pre-trade check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
feeNoFee amount to apply. Omit for the server default.
unitsNoRedemption units (shares to sell). Use for a sell / buy by units; mutually exclusive with `amount`.
actionYesOrder action: `buy` or `sell`.
amountNoSubscription amount (cash to invest). Use for a buy by amount; mutually exclusive with `units`.
remarkNoOrder remark / note.
executeNoThe `confirmation_code` from this order's dry run. WITHOUT IT NOTHING IS SENT. Omitted (the default) makes this a DRY RUN: the request is validated and echoed back with a three-digit `confirmation_code`, and nothing reaches the fund channel. Required protocol: call once without `execute`, show the returned preview to the user, and call again quoting the code only after the user has explicitly confirmed that exact order. The code is single use, expires in 10 minutes, and applies only to this exact order — change any field and it stops working. Never quote it back on your own initiative, and never in the same turn the user first asks.
currencyYesOrder currency, e.g. `HKD`, `USD`.
counter_idYesFund counter_id, e.g. `UT/FD/HK0000384492` (from `fund_hot` / `fund_list`).
is_sell_allNoSell the entire held position; overrides `units` for a full redemption.
trade_methodNoTrade method selector (server-defined). Omit for the default.
dividend_optionNoDividend handling option (server-defined, e.g. reinvest vs. cash payout).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.13.2

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that without execute nothing is sent, that the confirmation code is single-use, expires in 10 minutes, and is bound to the exact order fields, and that auth is required. The destructive/openWorld/not-idempotent annotations are consistent with this and reinforced rather than repeated.

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

Conciseness4/5

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

Front-loads the dry-run protocol, then packs parameter semantics into a dense sentence. Every clause carries information, but the second half is a long run-on that could be split for scanability.

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?

For a 12-parameter destructive mutation with no output schema, the description covers the safety-critical protocol, the auth requirement, and the parameters whose interplay matters most; the remaining fields are fully documented in the schema. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real semantics the schema leaves implicit: counter_id provenance (fund_hot / fund_list), the amount-vs-units tradeoff ('cash to invest' vs 'shares to sell'), and is_sell_all overriding units. Fee, remark, trade_method and dividend_option are left to the schema.

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?

States a specific verb and resource ('Submit a fund buy/sell order') and is immediately distinguishable from the stock sibling submit_order and from fund_validate_order. An agent knows exactly what domain object this acts on.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use protocol (dry run first, show preview, re-call with the code only after explicit confirmation) and names the alternative pre-trade tool: 'Use fund_validate_order first for a safe pre-trade check.' Both the workflow and the sibling routing are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools