Skip to main content
Glama

Deploy Strategy (Live Offline)

tt_deploy_strategy_paper

Deploy 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

NameRequiredDescriptionDefault
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only mark it non-read-only and non-idempotent, while the description explains the consequence of that non-idempotency (two calls create two deployments), the auth requirement (per-user connection; shared-key refused), the broker-attachment algorithm, the broker_connected_without_exchange refusal rule, and that evaluation starts on the next engine cycle. Nothing here contradicts the annotations.

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?

Well front-loaded: the capability statement comes first, then the confirmation rule, then guardrails, then args. It is long and repeats the 'not a test / not live' warning in several forms, which costs some efficiency, though each repetition guards a distinct failure mode an agent is likely to commit.

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?

For a mutating, non-idempotent, auth-gated tool with no output schema and an undocumented parameter, the description covers everything an agent needs: the input identity, what gets attached, what refusals mean, what to tell the user afterwards, and where to go if it breaks. No material gap remains.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the parameter, and it does: strategy_id is the TEMPLATE id (from tt_create_strategy or an edit_url), explicitly not a deployed strategy SID. It also rules out parameters an agent might expect to supply (exchanges come from the legs, broker is not a choice).

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?

States a specific verb and resource (deploy a strategy template) plus the exact execution mode (Live Offline) and its defining constraint (no orders placed). It also explicitly forecloses confusion with a hypothetical live-deploy tool, so an agent can distinguish it from siblings like tt_backtest_strategy without opening a 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?

Gives an explicit precondition (confirm with the user first, because the call is not idempotent), a prerequisite step (call tt_get_my_brokers first to name the broker that will attach), and follow-up routing (tt_get_my_deployed_strategies to monitor, tt_diagnose_strategy on error). It also states which refusals are normal and should be relayed rather than retried.

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