Skip to main content
Glama
Sign In

TraderWAI

by com.traderwai
OverviewDiscussionsAdmin

Set Auto-execution Config (per symbol)

set_auto_execution_config
Destructive

Configure per-symbol auto-execution. When enabled for a symbol, TraderWAI's backend automatically executes suggested orders (from suggest_order) for that symbol on the chosen broker account(s) — the user does not have to review them. This is the same configuration available on the TraderWAI website. Creates or updates the config for the given symbol. Get broker account IDs with get_broker_accounts. Note: the take profit always comes from each suggestion, not from this config. Requires the global auto-execution switch to also be ON (see set_global_auto_execution).

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading symbol (e.g. EUR_USD).
enabledYesEnable (true) or disable (false) auto-execution of suggested orders for this symbol
maxPerDayNoSafety cap: max number of auto-executions per day for this symbol
brokerConfigsNoBroker account(s) where orders are auto-executed. Required when enabling.
skipIfOpenPositionNoIf true (default), do not open a new order when a position already exists for the symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Trading symbol (e.g. EUR_USD). Use list_symbols for options"New value: +"Trading symbol (e.g. EUR_USD)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / brokerConfigs / items / properties / confirmHighRisk
      Added value: +{
+  "description": "Only after the user explicitly confirmed a percentage risk above 10% per order",
+  "type": "boolean"
+}
    • changedInput schema / properties / brokerConfigs / items / properties / sizingMode / description
      Previous value: -"\"percentage\" = % of balance to risk (max 10), \"fixed_lots\" = fixed lot size"New value: +"\"percentage\" = % of the balance LOST if each order's stop loss is hit (not the share of the balance used); \"fixed_lots\" = fixed lot size"
    • changedInput schema / properties / brokerConfigs / items / properties / sizingValue / description
      Previous value: -"For percentage: 0.5-10 (%). For fixed_lots: lot size (e.g. 0.01)"New value: +"For percentage: typically 0.25-2 (%), up to 100; above 10 needs confirmHighRisk after the user confirms (each auto-executed order risks this %, so 10 orders at once = 10×). For fixed_lots: lot size (e.g. 0.01)"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag mutation, destructiveness, open-world behavior, and non-idempotency; the description adds critical behavioral context beyond that, including that orders may execute without user review, that take profit comes from each suggestion rather than this config, and that a global switch is a prerequisite. Nothing contradicts the annotations.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and then adds only material caveats: auto-execution behavior, global prerequisite, broker account lookup, and take-profit source. Each sentence contributes to correct invocation or risk understanding, with no obvious filler.

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 destructive per-symbol configuration mutation, the description covers the key operational context: what it configures, that it creates or updates, the global prerequisite, where broker IDs come from, and the important take-profit caveat. Given the fully documented schema and rich annotations, an agent has enough information to invoke it correctly.

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?

The input schema has 100% description coverage, so parameter meaning is already fully documented. The description adds useful context around broker accounts and the global switch prerequisite, but it does not add parameter-level detail beyond what the schema already supplies, making 3 the appropriate baseline.

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?

The description states a specific verb and resource: configuring per-symbol auto-execution. It explains what activation does (backend auto-executes suggested orders without user review) and distinguishes this per-symbol config from the sibling global auto-execution switch.

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?

It gives clear usage context: enabling causes auto-execution on chosen broker accounts, broker IDs come from get_broker_accounts, and the global auto-execution switch must also be ON via set_global_auto_execution. It does not explicitly state when not to use this tool or contrast it directly with delete/get config siblings, so it falls short of full 5-level routing guidance.

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