Skip to main content
Glama

Suggest Order (order to authorize — the user decides)

suggest_order

PROPOSE a trade for the user to authorize, instead of placing it yourself. You never move the user's money with this tool: you only create an "order to authorize" (entry, stop loss, take profit, expiration) and the USER authorizes its execution. Use it whenever you should not or cannot place trades directly — e.g. your policy does not allow executing real-money trades, or the user wants to review first. (To place an order directly and immediately, when allowed and requested, use execute_trade.) Get the broker's current price with get_quote first and compute entry, stop loss and take profit from it (a SELL LIMIT above the bid, a BUY LIMIT below the ask). For breakout entries use create_conditional_order.

What happens next depends on the user's own settings in TraderWAI: (1) No auto-execution for this symbol: TraderWAI notifies the user (email / browser) and the order waits in "Orders to authorize" until they authorize it, reject it, or it expires. Nothing is executed without their action. (2) The user enabled auto-execution for this symbol: TraderWAI executes it on their broker following the rules the user configured (account, size, daily limits), and notifies them.

Tell the user which case applies if you know it, and remind them they can automate a symbol from the notification. Provide concrete price levels as full numbers (e.g. 1.09542 / 95432.50) and an expiration. Available on all plans.

Input Schema

NameRequiredDescriptionDefault
notesNoBrief trade rationale shown to the user
sourceNoIdentifier of the AI making the suggestion (e.g. "claude", "fable")
symbolYesTrading symbol (e.g. EUR_USD).
stopLossYesStop loss price level (full price, no abbreviations)
expiresAtNoAbsolute ISO 8601 expiration (overrides expiresInHours)
orderTypeYesLONG = buy, SHORT = sell
confidenceNoConfidence 0-100
entryPriceNoReference/expected entry price (current market price for MARKET)
limitPriceNoRequired for LIMIT orders: the desired entry price level
takeProfitYesTake profit price level (full price, no abbreviations)
executionTypeYesMARKET = at current price, LIMIT = at a specific price
expiresInHoursNoHours until the suggestion expires (1-72, default 24). Ignored if expiresAt is set
riskRewardRatioNoComputed risk:reward ratio

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. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond annotations, it explains the authorization flow, notification behavior, expiry, and user-configurable auto-execution. The phrase 'you never move the user's money' is slightly overbroad because case 2 can execute on the broker, but the description immediately qualifies that behavior.

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?

The purpose and alternatives are front-loaded, and the numbered case breakdown is structured and useful for explaining auto-execution. It is somewhat long and repeats the user-authorization idea, so it is not maximally concise.

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 13-parameter tool with no output schema, the description covers the critical decision context and post-call behavior, including both authorization and auto-execution paths. An agent has enough information to select and invoke the tool correctly.

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 practical semantics: compute entry, stop loss, and take profit from get_quote; use SELL LIMIT above the bid and BUY LIMIT below the ask; provide full numbers and an expiration. It does not elaborate on notes, source, confidence, or riskRewardRatio, though those are already documented in 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?

The opening sentence gives a specific verb and resource: 'PROPOSE a trade for the user to authorize, instead of placing it yourself.' It explicitly contrasts this with execute_trade and create_conditional_order, so an agent can distinguish it from sibling order-placement tools.

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?

It states explicit conditions for use: when policy forbids real-money execution or the user wants to review first. It also names the alternative for direct placement and the sibling for breakout entries, and gives a required pre-step to call get_quote before computing price levels.

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