Skip to main content
Glama

Preview Change Impact

tt_preview_change
Read-onlyIdempotent

⭐ 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

NameRequiredDescriptionDefault
patchNoOptional 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.
valueNoThe specific hard-coded value to drill into, e.g. '1m' for dimension='timeframe'. Only meaningful together with `dimension`.
dimensionNoNarrow the map to ONE dimension so its full site list is reachable past the 25-site cap. Pair with `value`.
max_sitesNoRaise the per-value site cap from its default of 25. Clamped to 1..500.
strategy_idYesTemplate id of the strategy to map. A deployment SID is auto-resolved to its template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds substantial context beyond that: it explains truncation caps, exact counts versus capped listings, occurrence collapsing within one condition, cross_layer and traps output, partial_change_findings, and the machine-checked unchanged list. It also clarifies that a deployment SID is auto-resolved to its template.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core instruction and clearly structured around two modes and drilling behavior. However, it is quite long and includes some repetition of read-only/free behavior already covered by annotations, plus emphasis that could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return behavior. It does so thoroughly: dependency map fields, cross_layer, traps, partial_change_findings, unchanged, occurrence details, and truncation reporting. An agent has enough context to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter descriptions already carry baseline meaning. The tool description still adds useful behavioral semantics: patch is the same RFC-6902 op list tt_apply_strategy_patch takes, dimension and value drill into one value past the 25-site cap, and max_sites raises that cap up to 500. It does not fully restate every parameter, but it meaningfully supplements how they interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: preview change impact before editing an existing strategy. It sharply frames the unique question it answers—where a value is hard-coded and what else moves with it—and distinguishes the tool from apply-style siblings by emphasizing preview versus actual write.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance: call before editing an existing strategy, especially one with a Python block, and use it to answer the user honestly before patching. It also explains the strategy_id-only versus strategy_id+patch modes. It does not explicitly name when not to use this tool or route to alternatives such as tt_apply_strategy_patch for the actual write.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources