Skip to main content
Glama

Export Strategy

tt_export_strategy

Export a strategy as a downloadable ASB-importable JSON file.

Fetches the strategy, frames it into the tt-strategy/v2 export format (the same format Tradetron's ASB Import button reads), stages it behind an unguessable link, and returns the download URL.

THE LINK IS A BEARER LINK, by design, so a browser can click it without a sign-in: it carries no auth, and anyone who has the URL can download the strategy until it expires, 24 HOURS after creation. (A reports export gets six hours instead — trade history is a different risk class from a strategy definition.) Worth a word when you hand it over if the strategy is not one they would publish.

Use when the user wants to save a strategy's JSON locally, share it, or import it into a DIFFERENT Tradetron account (download the file, then Tradetron → strategy builder → Import). Accepts a template id (eight digits, currently beginning 10) or a deployed SID (auto-resolved to its template). Do NOT tell the two apart by shape — both are 8-digit numbers now.

ALWAYS show the user the returned download_url as a clickable link, plus the expiry, and every entry in warnings (per-account list references, embedded python) verbatim.

NOTE: the exported file is the ASB IMPORT format (camelCase), NOT the shape tt_create_strategy accepts — never feed it back into tt_create_strategy / tt_update_strategy. To copy a strategy within the SAME account, send the strategy body from tt_get_strategy(id), with a new name, to tt_create_strategy (dry_run=true first): create converts it and strips the live row ids, and reports both. Never copy row ids into a hand-built payload — that is what reassigns the original's rows.

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

Input Schema

NameRequiredDescriptionDefault
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, which is consistent with staging an unguessable public link. The description goes well beyond them: it discloses that the link is a bearer link requiring no auth, that anyone with the URL can download until expiry, the exact 24-hour lifetime, the per-call `warnings` payload (per-account references, embedded python), and a caveat about handing it over for a non-public strategy. That is exactly the risk context annotations cannot convey.

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?

It is long but front-loaded: action, mechanism, then risk, then usage, then the format-mismatch caveat. Almost every sentence carries decision-relevant information, though the parenthetical about the reports export's six-hour lifetime is an aside that could be trimmed without losing anything an agent needs.

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?

Despite having no output schema, the definition fully describes the return contract (a `download_url`, an expiry, and a `warnings` list that must be surfaced verbatim) and the required user-facing rendering (clickable link plus expiry plus all warnings). It also closes the most likely misuse path by contrasting the camelCase ASB import format with the shape tt_create_strategy expects.

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 description coverage is 0% and the single parameter is documented only as "Strategy Id", so the description must carry the burden — and it does, explaining that it accepts either a template id (eight digits, currently beginning 10) or a deployed SID that is auto-resolved to its template, plus the key warning not to distinguish them by shape since both are 8-digit numbers. It stops short of giving an example value or stating what happens when an SID resolves to multiple templates.

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 opening sentence names the specific verb and artifact ("Export a strategy as a downloadable ASB-importable JSON file") and the second sentence details the mechanism (fetch, frame into `tt-strategy/v2`, stage, return URL). It is immediately distinguishable from tt_get_strategy or tt_create_strategy, which are named later.

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?

It gives explicit when-to-use triggers (save locally, share, import into a DIFFERENT Tradetron account), names the alternative path for the same-account case (send tt_get_strategy's `strategy` body to tt_create_strategy with dry_run=true first), and includes a hard "never feed it back into tt_create_strategy / tt_update_strategy" exclusion. This is the full when/when-not/alternative triad.

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