Skip to main content
Glama

Get Strategy

tt_get_strategy
Read-onlyIdempotent

Fetch an existing strategy template from Tradetron.

Returns the flat EDITABLE representation — the shape tt_update_strategy accepts.

TO COPY A STRATEGY IN THE SAME ACCOUNT: prefer tt_create_strategy(copy_from_strategy_id=): no body to send. Or send this result's strategy body, with a new name, to tt_create_strategy (dry_run=true first). Create converts a read body to the create shape itself — the read's own field types ("Month", "0.00", "Continuous"), the read-only keys, the universal set's missing list, TT's derived condition_action (any runtime-variable write held only there is moved into a Set Runtime Var row with the same expression) and the row ids — and reports every change in copy_conversion. Conditions, legs, Init Vars, tags and the python_code are carried as read. Do not edit the body by hand to get past an error: what create still refuses is a defect in the SOURCE strategy (this result's validation block lists the same findings), and the copy would inherit it. To copy onto another underlying, create the copy first, then change it with tt_apply_strategy_patch (tt_preview_change lists every site).

summary_md is a READ-BACK summary for showing the user: it is not create input and does not parse as strategy markdown. It names the python block's size but not its code.

Use it before tt_update_strategy to see the current state.

SNAPSHOT BEFORE YOU EDIT. There is no rollback anywhere in this MCP — keep this result if you are about to write. It is also the fastest health check on a strategy: the stored payload is re-validated on every read, so anything already wrong surfaces here.

THIS BODY CARRIES LIVE DATABASE ROW IDS — see row_identity_notice on the result. They are for UPDATE only: tt_update_strategy / tt_apply_strategy_patch match rows on id, and dropping them re-mints every row and orphans live deployments' open positions. Do NOT hand-assemble a tt_create_strategy payload out of this body: Tradetron's create matches conditions and legs on the same ids with no ownership check, which is how template 6008570 (195 subscribers) was emptied into a new template on 2026-09-20. tt_create_strategy strips those ids itself (reported in row_identity_stripped), which is why sending this body UNCHANGED is the copy route above. Never remove condition_action by hand either: a template can hold its runtime-variable writes only there, and create moves them into Set Runtime Var rows; deleting the key loses them.

Every set, condition and leg uuid here is minted fresh by Tradetron on EACH read (it is not stored), so it changes between two reads of an unchanged strategy. Match rows by id (condition and leg ids are stable; set ids change on every save) or by type+content, never by uuid.

Expect scaffolding you did not author. Create and patch INJECT blank Add Repair / Exit condition envelopes into each set, so the sets you read back carry more conditions than you wrote. Every strategy also ENDS with Tradetron's universal set — Add Repair, a hidden (visible: 0) Repair Once / Overnight Protection envelope, then the Universal Exit — whether or not a Universal Exit was authored; unauthored, that Universal Exit is blank and never fires (summary_md says "No Universal Exit configured"). The hidden Overnight Protection envelope is TT's skeleton, not a feature you authored or can rely on. Templates created before 2026-09-17 with no authored UE lack the universal set, and TT grafts that envelope onto their LAST working set instead. They are inert placeholders — not content loss, not a bug. Anyone diffing a before/after without knowing this files a phantom bug on their first attempt (the note previously existed only on tt_apply_strategy_patch, which is not where users first hit it).

Known limitations worth reading before a structural edit:

  • No rollback and no version history. Your snapshot is the backup.

  • tt_validate_markdown DOES judge a tt_export_strategy file: it un-frames the v2 format and runs the import gate, answering route "asb_import" with the codes ASB Import itself uses. Validate BEFORE importing; call THIS tool after, as a read-back.

  • A same-exchange underlying swap that leaves expiry/strike/ strike_json/strike_display/instrument on the old symbol is refused (LEG_SYMBOL_REFERENCE_DESYNC). Re-derive them in the SAME write.

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_get_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Well beyond the readOnly/idempotent annotations, it discloses non-obvious behavior: uuids are re-minted on every read and must not be used for matching, the stored payload is re-validated on read so errors surface here, and there is no rollback anywhere in the MCP. Credit is slightly reduced because a large share of the behavioral text (row-id stripping, LEG_SYMBOL_REFERENCE_DESYNC, copy_conversion) actually describes sibling write tools rather than this read, and the return surface (validation, row_identity_notice, summary_md) is described in fragments rather than systematically.

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

Conciseness2/5

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

Purpose and copy route are front-loaded, but the bulk is a sprawling incident narrative (the 6008570 postmortem, scaffolding archaeology, a note explaining why a note was previously misplaced elsewhere). Several paragraphs govern tools other than this one and should live on those tools, forcing the agent to filter signal from a very long block before calling a one-parameter read.

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

Completeness4/5

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

For a one-param read with no output schema, it covers the essentials an agent needs (snapshot-before-edit, live row ids, uuid instability, scaffolding you did not author), so nothing required to call or interpret the result is missing. It over-delivers on adjacent write-tool caveats and under-delivers on the strategy_id domain, which keeps it short of a 5.

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

Parameters3/5

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

One parameter, strategy_id, with 0% schema description coverage, and the description never defines it — it does not say whether this is a template id, a subscription id, or a deployed-strategy id, despite tt_get_my_deployed_strategy_detail existing as a sibling. The mention of "template 6008570" and "template" language gives weak implicit hints, but the agent must infer the identifier's domain.

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?

Opens with a specific verb+resource: "Fetch an existing strategy template from Tradetron," and immediately characterizes the return as "the flat EDITABLE representation — the shape tt_update_strategy accepts." That distinguishes it from tt_create_strategy, tt_update_strategy, and tt_export_strategy without the agent needing to open any schema.

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

Usage Guidelines5/5

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

Explicit routing is given: "Use it before tt_update_strategy to see the current state," and for copying, "prefer tt_create_strategy(copy_from_strategy_id=<id>): no body to send." It also states a when-not (do not hand-assemble a create payload from this body) and positions it relative to tt_validate_markdown ("Validate BEFORE importing; call THIS tool after, as a read-back").

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