Backtest Result
tt_backtest_resultA finished backtest's NUMBERS — the figures from its own report, as data.
THIS IS FREE. It reads a run the user has already paid for; no engine runs and nothing is charged, however many times it is called. Slice the same run as often as the question needs.
Use it the moment tt_backtest_status says done. tt_backtest_status returns a report_url and no figures, on purpose; this is how you read them without a browser. tt_backtest_trades remains the way to page raw FILLS — this gives you the analysis over them.
Sections (ask by name; the default set is the cheap ones): headline meta costs weekday drawdowns monthly exit_attribution concentration trade_stats setwise stats_table <- default series sub_windows grade timing distribution underwater regime rom benchmark walk_forward montecarlo quality trades positions sets underlyingwise
underlyingwise is P&L, trades and ROI PER UNDERLYING — the same split the
report page renders under BREAKDOWNS -> Underlying-wise. Ask for it on any
multi-instrument book: the default response announces it in
section_notes.underlyingwise when the run holds more than one. Do not
re-derive it by paging trades.
sub_windows is summarised by default — six trailing windows are six
COMPLETE nested results (measured: 91 KB on a 42-trade run). Each block
names what was dropped under _omitted, and section_notes reports
approx_chars. Pass caps={"sub_windows_full": true} for the whole blocks.
THREE THINGS THIS DELIBERATELY DOES NOT DO, and you must respect them:
caveats[]is not decoration. Each entry names, inaffects, the metric keys it taints. Read it BEFORE quoting any figure. Never present a run carrying a high-severity caveat as evidence of an edge.A risk-adjusted figure the book cannot support is ABSENT, not zero — see
section_notes.headline_withheldfor which and why. Do not fill the gap from the report page, and do not estimate it.section_notes.<name>.basissays whether a section is gross or net. The headline is net; Monte Carlo, PSR, timing and distribution are gross. Never put a net figure and a gross one in the same sentence without saying so.
A section marked single_trial (montecarlo, quality/PSR) assumes ONE
backtest was run. After comparing variants it reads high by construction
and is not a probability that the strategy works. Say that, or omit it.
Args: job_id: 'ttbt-...' or a bt_id from tt_list_backtests. sections: section names; omit for the default set. caps: per-section row caps, e.g. {"trades": 200}; plus {"sub_windows_full": true} to unsummarise the trailing windows.
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_id": "<job_id>"
},
"name": "tt_backtest_result"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| caps | No | Override a section's row cap, e.g. {"trades": 200}. Raise only when you genuinely need the rows: `trades` is ~56k tokens in full. {"sub_windows_full": true} returns each trailing window's complete nested result instead of its summary. | |
| job_id | Yes | The run's job_id from tt_backtest_strategy ('ttbt-...') or its bt_id from tt_list_backtests. | |
| sections | No | Which parts to return. Omit for the default set, which answers most questions in ~2,400 tokens. Ask for more by name — see `available_sections` in any response. |