Skip to main content
Glama

get_backtest_progress

Read-only

Progress of a backtest started with start_backtest.

    Returns `{task_id, status, progress, message, dashboard_url}`;
    `status` is 'running', 'completed' or 'error' and `progress` 0-100.
    When the run has finished, the answer also carries `result`, the same
    summary `summarize_workflow` gives: the verdict in words and, for a
    run of a year or longer, a few rounded figures; and `report_url`, the
    report, which the run's card in the chat shows. A rule that ran as a
    circuit of the lab's cards answers here as get_primitives_run_progress
    answers it.
    

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": {
      "task_id": "<task_id>"
    },
    "name": "get_backtest_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing the return shape, the 'running'/'completed'/'error' status enum, the 0-100 progress range, and what extra fields appear on completion (result, report_url). This is meaningful behavioral context annotations don't provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The return-shape sentences are front-loaded and useful, but the final two sentences are wordy and confusing ('A rule that ran as a circuit of the lab's cards...'), adding ambiguity rather than clarity.

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?

With no output schema, the description does the work of explaining return fields, statuses, and completion behavior, which is largely sufficient for a polling/progress tool. Minor gap is the lack of explicit polling/stop guidance.

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?

One required param (task_id) at 0% schema coverage, so the description must carry the burden. It only obliquely indicates task_id originates from start_backtest and gives no format detail, leaving the parameter under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('progress of a backtest') and ties it to its origin tool 'start_backtest', letting an agent distinguish it from the many other progress tools. Clear without needing the schema, though it doesn't explicitly contrast with siblings like get_walkforward_progress.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage ('a backtest started with start_backtest') so the when-to-call is inferable, but it never states polling guidance, when to stop polling, or how it differs from the similar *-progress siblings. Usage is implied rather than stated.

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