Skip to main content
Glama

Backtest Workbench

tt_backtest_workbench
Read-onlyIdempotent

OPEN A STRATEGY FOR BACKTEST WORK. Start here, not with a submit.

Give it a template id and it answers, in one call: is this yours, what has already been run on it, what those runs can tell you for FREE, and what a new run would cost. AUTH-REQUIRED. It never submits and never charges.

WHY IT MATTERS: reading and re-slicing a run the user already paid for is free and unlimited; a NEW run is a fresh charge. You cannot tell which side a question falls on without knowing what runs already exist — so a model that skips this either re-buys a backtest the user already has, or refuses to explore because it assumes everything costs. Both waste the user's money or their time.

HOW TO USE THE ANSWER:

  • runs.rows with finished: true → answer from these first, via tt_backtest_result. Slice them as many times as the question needs.

  • next_run.changes_that_need_one is the definitive list of what forces a new paid run: the strategy body, the dates, the type, the expiry, the fill price, the candle frequency. NOTHING ELSE DOES.

  • next_run.quote is Tradetron's own price. Quote it verbatim; never compute or estimate one, and never state a price when it is null.

TEMPLATE_NOT_YOURS is terminal — do not retry the id, and do not guess another. Ask the user, or call tt_list_my_strategies.

Args: template_id: the strategy template to open. start/end: only needed to price a prospective new run. run_limit: past runs to list (default 20, max 100).

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": {
      "template_id": "<template_id>"
    },
    "name": "tt_backtest_workbench"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWindow end YYYY-MM-DD, same purpose.
startNoWindow start YYYY-MM-DD, only to price a prospective new run. Omit if you just want to see what already exists.
run_limitNoHow many past runs to list. Default 20, max 100.
template_idYesThe strategy template id to open. From tt_list_my_strategies, or the number in a /strategies/<id>/edit URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description corroborates rather than contradicts them ('never submits and never charges', 'AUTH-REQUIRED'). Beyond the annotations it discloses the cost model — re-reading existing runs is free and unlimited while a new run is a fresh charge — and enumerates the exact fields that trigger a paid run via next_run.changes_that_need_one, plus a quoting rule for prices ('quote verbatim; never compute... never state a price when it is null').

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?

Front-loaded with the imperative and the anti-pattern in the first line, then organized into clearly labelled blocks for interpretation and arguments. The 'WHY IT MATTERS' paragraph is the least economical part — it argues a rationale at some length — but it does carry the cost-model insight that prevents wasted spend, so it mostly earns its space.

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?

There is no output schema, so the description must carry the return contract, and it does: it names runs.rows with finished, next_run.changes_that_need_one, and next_run.quote, and tells the agent how to act on each. Combined with auth and terminal-error handling, nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100%, so the parameters are already fully documented. The description's args block largely restates the schema (start/end only for pricing a prospective run, run_limit default 20 max 100) rather than adding new meaning, so the baseline 3 applies.

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 — 'OPEN A STRATEGY FOR BACKTEST WORK' — and immediately scopes it against the wrong first move ('Start here, not with a submit'). It further names what the call returns (ownership, existing runs, free re-slicing, price of a new run), so an agent can distinguish it from tt_backtest_result or 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?

Explicit ordering guidance ('start here, not with a submit'), an explicit downstream route ('runs.rows with finished: true → answer from these first, via tt_backtest_result'), and an explicit terminal-error path ('TEMPLATE_NOT_YOURS is terminal — do not retry the id... ask the user, or call tt_list_my_strategies'). When-to-use, when-not-to-use, and alternatives are all present.

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