Skip to main content
Glama

Execute Trade on Several Accounts

execute_trade_multi
Destructive

Place the SAME immediate order on several broker accounts at once (multi-account: Plus, Trader and Max): either an account group (accountGroup, see get_account_groups) or a list of brokerAccountIds. Groups can define the size per account (e.g. 0.5% risk on a prop firm account and 1 lot on a personal one); otherwise the quantity/sizing of this call is used for every account. Each account is checked against its own risk limits and uses 1 daily execution. For a single account use execute_trade.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "orderType": "<orderType>",
      "executionType": "<executionType>",
      "stopLoss": "<stopLoss>",
      "takeProfit": "<takeProfit>"
    },
    "name": "execute_trade_multi"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading symbol in TraderWAI format (e.g. "EUR_USD", "XAU_USD")
quantityNoLots for accounts without their own sizing in the group
stopLossYesStop loss price (absolute)
orderTypeYes"LONG" for buy, "SHORT" for sell
entryPriceNoRequired for LIMIT and STOP orders
sizingModeNoSizing for accounts without their own sizing
takeProfitYesTake profit price (absolute)
sizingValueNoWhen sizingMode="percentage", the % of each account balance LOST if the stop loss is hit (not the share of the balance used). Above 10 requires confirmHighRisk.
accountGroupNoName of an account group (get_account_groups). Use this or brokerAccountIds.
executionTypeYes"MARKET" fills now; "LIMIT" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); "STOP" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, eToro, Bybit, Toobit and Kraken — accounts on other platforms return an error, use create_conditional_order for them.
confirmHighRiskNoOnly after the user explicitly confirmed a percentage risk above 10% per order (tell them the total across accounts).
brokerAccountIdsNoIDs of the broker accounts (get_broker_accounts). Use this or accountGroup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / executionType / description
      Previous value: -"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, eToro, Bybit and Toobit — accounts on other platforms return an error, use create_conditional_order for them."New value: +"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, eToro, Bybit, Toobit and Kraken — accounts on other platforms return an error, use create_conditional_order for them."
  2. Changed1 schema field changed
    • changedInput schema / properties / executionType / description
      Previous value: -"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, Bybit and Toobit — accounts on other platforms return an error, use create_conditional_order for them."New value: +"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, eToro, Bybit and Toobit — accounts on other platforms return an error, use create_conditional_order for them."
  3. Changed1 schema field changed
    • changedInput schema / properties / executionType / description
      Previous value: -"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com and Bybit — accounts on other platforms return an error, use create_conditional_order for them."New value: +"\"MARKET\" fills now; \"LIMIT\" = pending pullback order at each broker (BUY LIMIT below the ask, SELL LIMIT above the bid); \"STOP\" = pending breakout order (BUY STOP above the ask, SELL STOP below the bid), only on TradeLocker, cTrader, MetaTrader, Capital.com, Bybit and Toobit — accounts on other platforms return an error, use create_conditional_order for them."
  4. Changed2 schema fields changed
    • addedInput schema / properties / confirmHighRisk
      Added value: +{
      +  "description": "Only after the user explicitly confirmed a percentage risk above 10% per order (tell them the total across accounts).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / sizingValue / description
      Previous value: -"When sizingMode=\"percentage\", the % of each account balance to risk"New value: +"When sizingMode=\"percentage\", the % of each account balance LOST if the stop loss is hit (not the share of the balance used). Above 10 requires confirmHighRisk."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructive=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description still adds real context beyond them: per-account risk-limit checks, the fact that each account consumes 1 daily execution, and that sizing above 10% requires confirmHighRisk after telling the user the cross-account total. It omits partial-failure behavior (what happens when some accounts reject the order), which matters for a fan-out destructive call.

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-loaded with the core action and scope, then targeting modes, then sizing precedence, then the sibling hand-off — a logical order with little waste. The opening phrase "immediate order" is slightly at odds with the LIMIT/STOP execution types later in the schema, which is a minor precision cost.

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?

For a 12-parameter destructive fan-out tool with no output schema, the description covers targeting, sizing precedence, risk checks and quota consumption well. Remaining gaps are partial-failure semantics and what the caller gets back per account, which the agent would otherwise have to discover empirically.

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 precedence semantics the schema only hints at: group-level sizing overrides the call-level quantity/sizing for accounts that define their own size, otherwise quantity/sizing applies to every account. It also clarifies accountGroup vs brokerAccountIds as mutually exclusive targeting modes.

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 with scope: "Place the SAME immediate order on several broker accounts at once", and enumerates the supported account types (Plus, Trader, Max). It explicitly contrasts with the sibling execute_trade for single-account use, so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

Gives the key routing rule ("For a single account use execute_trade") and points to get_account_groups and get_broker_accounts for the two targeting modes. It does not say when multi-account execution is inappropriate (e.g. differing orders or sizes per account beyond group sizing), so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources