Skip to main content
Glama

Promote To Strategy

tt_promote_to_strategy
Read-onlyIdempotent

Turn a rule set that survived tt_check_edge into a real, VALIDATED Tradetron strategy — as a draft. Creates nothing, charges nothing, deploys nothing.

trade says what to actually buy or sell: long_call, short_put, long_put, short_call, long_future, short_future. IT HAS NO DEFAULT. A rule says what the market is doing; it does not say whether you express that as a long call, a short put or a future, and those carry different risk. If the user has not said, ASK. A trade that contradicts direction is refused, not warned.

A PAID BACKTEST COMES BEFORE ANY DEPLOY, and say why: tt_check_edge traded the SPOT, so it cannot see what an options structure actually does. Tell the user the next steps are tt_create_strategy and then a backtest (tt_backtest_strategy, which is paid and quotes its price first); make each call only when the user asks for it. Deploying it (tt_deploy_strategy_paper: Live Offline, where Tradetron shows each signal and places no order) is the user's separate choice — never present it as a test or a step before going live.

Two behaviours to state without being asked, because the user cannot see them in the markdown: entry is GATED an hour after the open (at the open an intraday offset still points at yesterday's candles and would fire on stale data — the screen never measured that trade), and the set RE-ARMS after every exit, so it can round-trip repeatedly in a day.

A bars:N exit is refused: Tradetron has no "N bars after entry" primitive, and substituting a time exit would run something other than what was measured. Monthly-only roots never get a Current Week leg.

GOING LIVE IS NOT OFFERED and must not be suggested — it is a separate decision the user takes in Tradetron itself.

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": {
      "underlying": "<underlying>"
    },
    "name": "tt_promote_to_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotsNo
nameNo
rulesNo
tradeNoWhat to buy or sell: long_call, short_put, long_put, short_call, long_future or short_future. No default, because a rule says what the market is doing, not how to express it: a call without it is refused, naming it in details.missing_params.
directionNo'long' or 'short'.
exit_ruleNo
timeframeNo5m
underlyingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: entry is gated an hour after the open (with the stale-candle reason), the set re-arms after every exit, a bars:N exit is refused because Tradetron has no such primitive, monthly-only roots get no Current Week leg, and a trade contradicting direction is refused rather than warned. It also explains why readOnlyHint=true holds despite the 'promote' name ('Creates nothing, charges nothing').

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?

Purpose is front-loaded in the first sentence and the rest is organized as parameter rules, then next-step sequencing, then hidden behaviors, then the live-trading prohibition. It is lengthy and uses uppercase emphasis, but nearly every sentence carries a distinct constraint rather than restating the schema.

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 an 8-parameter, 1-required tool with no output schema, the description supplies the constraints an agent needs to call it correctly and to avoid the adjacent paid/destructive operations. The remaining gap is return-shape and the unaddressed parameters (lots, name, timeframe, underlying).

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?

With only 25% schema description coverage, the description must carry parameters — and it does well for `trade` (allowed values, no default, refusal behavior) and `exit_rule` (bars:N rejected) plus `direction` (contradiction refused). But `rules`, `underlying`, `timeframe`, `lots`, and `name` get no semantic treatment, leaving half the surface to the schema.

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 transformation (rule set that survived tt_check_edge → validated Tradetron strategy draft) and immediately bounds it with 'Creates nothing, charges nothing, deploys nothing', which disambiguates it from tt_create_strategy and tt_deploy_strategy_paper by name.

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: call tt_create_strategy next, then tt_backtest_strategy (noting it is paid and quotes first), and only when the user asks. It also states exclusions — deploy is the user's separate choice and going live is not offered and must not be suggested — so an agent has no ambiguity about what to do after this call.

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