Preview Change Impact
tt_preview_change⭐ CALL THIS BEFORE EDITING an existing strategy — especially one with a Python block. FREE, read-only, no wallet debit, no write.
Answers the question that nothing else can: where is this value hard-coded, and what else moves with it? A candle timeframe, an instrument, or a runtime variable is typically repeated across several conditions AND the Python block. Change some sites and not others and you get a strategy that validates clean, deploys, and trades a MIX of the old and new settings — the failure the caller will not see until live market.
Two modes:
• strategy_id alone — the DEPENDENCY MAP: every site where a
timeframe / instrument / runtime variable is hard-coded, grouped by
value, plus cross_layer (values living in more than one layer, the
ones a partial edit breaks), plus traps (validator findings
ALREADY present, so you learn this strategy's gotchas before
authoring rather than after a rejection).
• strategy_id + patch — the same for the resulting state, plus
partial_change_findings (sites your patch would leave behind) and
unchanged (a machine-checked "DO NOT CHANGE" list confirming the
dimensions you did not intend to touch really did stay put).
DRILLING IN. Two caps keep a large strategy from blowing the
response: each value lists at most 25 sites (truncated reports the
exact total), and each dimension lists at most 30 values, the ones
with the most sites (values_truncated reports the total). To see
EVERY site for one value, re-call with dimension, value and a
raised max_sites (both bounds are on the parameters themselves).
Counts are never filtered — n_sites/n_values always describe the whole
strategy, so a 145-variable strategy still reports 145 even when the
listing shows 30.
Sites that are genuinely identical — several reads of the same value
in ONE condition — carry occurrence and occurrences_at_path. The
payload has no finer locator than the path, so say "4 reads in that
condition", not four separate places.
Use it to answer the user honestly before you start: "1m appears in 4 places — 3 conditions and the Python block; changing it means changing all 4." Then patch all of them in ONE call.
patch is the same RFC-6902 op list tt_apply_strategy_patch takes, so
you can preview the exact patch you are about to apply.
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": {
"strategy_id": "<strategy_id>"
},
"name": "tt_preview_change"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| patch | No | Optional RFC-6902 op list — the same shape tt_apply_strategy_patch takes, e.g. [{'op': 'replace', 'path': '/sets/0/conditions/0/condition_json', 'value': '...'}]. Omit it for the plain dependency map; supply it to also get partial_change_findings and the machine-checked `unchanged` list. | |
| value | No | The specific hard-coded value to drill into, e.g. '1m' for dimension='timeframe'. Only meaningful together with `dimension`. | |
| dimension | No | Narrow the map to ONE dimension so its full site list is reachable past the 25-site cap. Pair with `value`. | |
| max_sites | No | Raise the per-value site cap from its default of 25. Clamped to 1..500. | |
| strategy_id | Yes | Template id of the strategy to map. A deployment SID is auto-resolved to its template. |