Quawd MCP Tool Reference

The anatomy of a strategy

Every Quawd strategy is assembled from a few kinds of parts. Each maps to a builder tool; the conditions themselves draw from the object reference.

Instruments

what it trades — one symbol, a basket, or a portfolio of strategies, on a chosen timeframe. → builder_create

Signals & logic

the conditions that drive it, attached to three roles — gate (allow / block), entry (open a position), exit (close one) — and combined with AND / OR / sequence. Protective stops and targets live here too, as exit conditions. → builder_add_condition, builder_compose → builder_attach · conditions & value refs

Sizing & policy

capital per trade, position accumulation, order type, and a daily-loss circuit breaker. → builder_set_strategy_config

Allocation

for baskets and portfolios — how capital is weighted across instruments or members, and when it rebalances. → builder_set_allocation → describe_allocation

Custom levels

anchor a candle or define a named price zone to reference inside conditions. → builder_save_anchor → builder_save_zone

Compile

freeze the assembled strategy into a runnable blueprint. → builder_compile

Once compiled, a strategy is validated (Backtesting & Validation) and can be deployed (Paper Trading).

How an agent builds one

A mean-reversion strategy, end to end:

1. 1builder_create — a new strategy on SPY, 1h bars.
2. 2builder_add_condition → builder_attach — an RSI(14) < 30 condition, attached as entry — buy oversold.
3. 3builder_add_condition → builder_attach — RSI(14) > 55 as an exit, plus a 3% stop_loss card as a protective exit.
4. 4builder_set_strategy_config — 10% of equity per trade.
5. 5builder_compile — freeze it into a runnable blueprint.
6. 6run_backtest — a one-year lookback to see how it would have done.