validate_strategy_versionRun the automated validation pipeline — syntax check, entry/exit logic check, and a quick real-data backtest on the version's own primary timeframe and MTF config — against the current draft version of one of your strategies. Required before that version can be promoted to the stable channel.
| Name | Type | Description |
|---|---|---|
id | string | Strategy ID whose latest/draft version to validate |
exchangeId | string | An exchange you own, used only to source historical candle data |
symbol | string | Trading pair to validate against, e.g. BTC/USDT |
timeframe | string | Backtest timeframe override (1m to 1w); defaults to the version's own primary timeframe |
days | number | Backtest length override, 1-90 days; defaults to a bounded window for the timeframe (about 2,160 candles, capped at 90 days) |
Try asking your AI assistant any of these:
list_strategy_versionsList the full version history for one of your own strategies — every stored version, its validation
compare_strategy_versionsBacktest a new version of one of your strategies and the current stable version on the same candles,
promote_strategy_versionPromote a specific version of one of your strategies to the stable or beta channel. Promoting to sta
update_strategyUpdate one of your own strategies — name, description, category, tags, or the code itself. Code edit
Set up the TradeStaq MCP server in under a minute.