Skip to main content
Glama

My Backtests

tt_list_backtests
Read-onlyIdempotent

The signed-in user's own Tradetron backtests — the same runs the website's Backtests page lists. AUTH-REQUIRED (returns the connect funnel if not authenticated).

THE id RESOLVER for backtests. tt_backtest_status needs a job_id and only a SUBMIT ever handed one out, so a run the user did not write the id down for was unreachable here. Call this whenever the user refers to a backtest you have no id for — "how did my backtest go", "the one I ran yesterday", "show me my backtests" — instead of asking them for an id.

Each row carries: job_id pass straight to tt_backtest_status. bt_id pass straight to tt_backtest_trades for the fills. finished TRUE completion. Use THIS, not status: a Tradetron backtest reads 'active' from the moment it is handed to the engine (4,206 of 4,218 rows in a week), so status cannot tell you whether a run is done. name, template_id, start, end, submitted_at. NOT report_url: this endpoint has never returned one, on a finished row or any other — 23 rows reading finished:true carried no such key. The link exists, and tt_backtest_status returns it for the same run; poll a row's job_id for it rather than looking here. backtesting_row_id NOT a run id — Tradetron's own database row id, which is bt_id minus the six-digit submit date. It is kept so nothing the endpoint sent is lost, and the three tools that take a run id do NOT agree about it: the status route refuses it as malformed, the trades route accepts it, and the result route accepts it for some runs and refuses it for others. Never pass it anywhere. Use job_id or bt_id, which are on the same row.

Carries NO performance figures — do not report a P&L from this listing. For the numbers use tt_backtest_trades or the row's report_url.

Args: limit: rows to return (default 20, max 100). offset: rows to skip; has_more and next_offset page the rest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_list_backtests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return. Default 20, max 100.
offsetNoRows to skip, for paging. Default 0.
template_idNoNarrow to one strategy template's runs. Filtered server-side, so an old run on a specific template is reachable even for a user with thousands of backtests.

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 already cover read-only/idempotent safety, yet the description adds substantial unseen context: AUTH-REQUIRED with a connect funnel, the warning that `status` reads 'active' for essentially every row so `finished` is the real completion signal, and the fact that `report_url` is never returned here with a documented count of missing rows. It also flags `backtesting_row_id` as a trap with per-route behavior differences — exactly the kind of hazard an agent cannot infer from structured fields.

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 and well organized: identity/intent first, then the resolver rationale, then a field-by-field hazard list. It is long, and the trailing Args section largely restates the schema, so some trimming is possible, but nearly every sentence carries decision-critical information.

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?

No output schema exists, and the description compensates by enumerating the returned fields (job_id, bt_id, finished, name, template_id, start, end, submitted_at) and explicitly naming what is absent (report_url, performance figures). An agent can call this and interpret the response without further discovery.

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 coverage is 100%, so baseline is 3, but the description adds paging semantics not in the schema ("`has_more` and `next_offset` page the rest") plus the default-20/max-100 shape in prose. It omits `template_id` from its Args block, leaving that one entirely to the schema, which keeps it from a 5.

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 scoped resource ("the signed-in user's own Tradetron backtests") and anchors it to the website's Backtests page so the agent knows exactly which dataset this is. It also explicitly positions itself as "THE id RESOLVER for backtests," which separates it from tt_backtest_status and tt_backtest_trades in one line.

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 explicit trigger phrasing ("how did my backtest go", "the one I ran yesterday", "show me my backtests") and an explicit behavioral instruction to call this instead of asking the user for an id. It also routes downstream: job_id to tt_backtest_status, bt_id to tt_backtest_trades, and numbers to those tools rather than this listing.

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