Skip to main content
Glama

TraderWAI

by com.traderwai
OverviewDiscussionsAdmin

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.

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 and Bybit — 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. 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."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With destructiveHint=true and non-idempotent=true already declared, the description still adds real value: per-account risk-limit checks, consumption of one daily execution per account, the confirmHighRisk gate above 10%, and the platform restriction on STOP orders. What it does not disclose is failure semantics when only some accounts succeed, which matters a great deal for a fan-out write.

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 the account-selection mechanism, then the caveats. Dense but every clause carries information; the one blemish is calling it an 'immediate order' while later supporting LIMIT and STOP pending orders, which reads slightly inconsistent.

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 write with no output schema, the description covers the selection, sizing, risk-gating and platform-constraint dimensions well. The remaining gap is the return/partial-failure story — an agent cannot tell whether a multi-account call returns per-account results or aborts on first failure.

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 baseline is 3, but the description adds genuine meaning: quantity/sizingValue apply only to accounts lacking their own group sizing, and sizingValue is the percent of balance lost at the stop rather than capital deployed. That resolves the most likely misreading of 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 (place the same order on several broker accounts) and immediately names the distinguishing scope: multi-account versus single. It explicitly routes to execute_trade for the single-account case, which is the exact sibling an agent would confuse it with.

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 concrete selection criteria: use accountGroup or brokerAccountIds, use execute_trade for one account, and use create_conditional_order for STOP orders on unsupported platforms. It also explains what happens when the group has no per-account sizing (the call's quantity/sizing applies). Little is left to inference.

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

All TraderWAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources