Compare Backtests
tt_backtest_comparePut two or three finished backtests side by side. FREE — reads runs already paid for, runs no engine, charges nothing.
This is the second half of research. One run tells you what happened; the comparison tells you whether the change you made did anything.
READ attribution BEFORE ANY NUMBER, and say what it says. A delta is
attributable to a cause only when EXACTLY ONE run input differs — the
window, the candle frequency, the type, the expiry, the fill price or
the strategy. If more than one moved, this is two different experiments
and no difference can be pinned on any of them. If none moved, the gap
is the engine's own run-to-run variation, not a result.
THERE IS NO WINNER FIELD, deliberately. "Which is better" over a short window is how people talk themselves into noise. You get deltas, a paired daily-difference test, and the job of drawing the conclusion in the open.
daily_test.verdict is not a footnote — quote it alongside the delta.
A bigger number over a few dozen days is usually chance, and the test
says so.
Metrics in not_compared were withheld on one side for being
unsupportable; subtracting them would launder them back in. Never do it.
Args: job_ids: 2-3 ids; the first is the baseline. sections: extra sections per run.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"job_ids": "<job_ids>"
},
"name": "tt_backtest_compare"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_ids | Yes | Two or three run ids to compare. The FIRST is the baseline; the rest are variants measured against it. | |
| sections | No | Extra sections to pull for each run. headline, meta and series are always fetched. |