Deploy Strategy (Live Offline)
tt_deploy_strategy_paperDeploy one of the user's own strategy templates in Tradetron's LIVE OFFLINE mode — Tradetron runs it on live prices and shows each signal; it places no order (the user may place one at their broker). Never present it as a test, practice or rehearsal.
CONFIRM WITH THE USER FIRST. Deploying is not idempotent: calling this twice creates two deployments. Say which strategy you're about to deploy and wait for a clear yes.
LIVE OFFLINE ONLY. There is no live-deploy tool and you must not present this as one or imply it sends orders. Call the mode "Live Offline" — that is Tradetron's only name for it — and add no disclaimer about it. You cannot switch it to Live Auto — but do not stonewall the question: going live is the user's own step, on the strategy's edit page (/strategies//edit), via Deploy -> broker, multiplier, and Live Auto as the execution type. Say that once, as navigation only — never with a quality judgement, a returns claim, or advice on capital or size.
Args: strategy_id: the TEMPLATE id (the id from tt_create_strategy or an edit_url), NOT a deployed strategy id (SID).
The exchanges are read from the strategy's own legs, so you don't pass
them. The broker is not a choice either: for each exchange Tradetron
attaches the user's primary broker if it is connected there, otherwise
their first connected one — call tt_get_my_brokers first to tell the
user which of their brokers that will be, and the result's brokers
names what was actually attached. "Connected there" means Tradetron
holds that exchange for the broker; a broker connected with no
exchange on record is not picked (the refusal then names it and its
rule is broker_connected_without_exchange). Two refusals are normal
and worth relaying as-is rather than retrying: the account has no
broker for the strategy's exchange, and a strategy whose legs have no
instrument set can't get a broker attached. Tradetron's typed
refusals (broker, instrument, quota) carry rule, the guard that
fired.
The tool name and the code STRATEGY_DEPLOY_NO_PAPER_BROKER are legacy identifiers, kept so existing clients keep working; both mean Live Offline. Never use their older wording with the user.
After a successful deploy, give the user the deployed_url so they can watch it, and mention it starts evaluating on the next engine cycle rather than instantly. Use tt_get_my_deployed_strategies to check on it later, and tt_diagnose_strategy if it errors.
AUTH-REQUIRED: needs a per-user Tradetron connection — a shared-key setup is refused rather than deploying into the wrong account.
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_deploy_strategy_paper"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| strategy_id | Yes |