Skip to main content
Glama

get_walkforward_progress

Read-only

Progress of a walk-forward started with start_walkforward.

    Returns `{task_id, status, progress, message, dashboard_url}`;
    progress moves window by window. When the run has finished, the answer
    also carries `result`, the same summary `summarize_workflow` gives, 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_walkforward_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?

Annotations already cover read-only and non-destructive, and the description adds real value beyond them: the exact return fields ({task_id, status, progress, message, dashboard_url}), the per-window progress semantics, and the extra `result` and `report_url` that appear only after completion. It stops short of disclosing error behavior for unknown/stale task_ids.

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 core return shape is stated early, but the closing sentence about 'a rule that ran as a circuit of the lab's cards' is convoluted and adds ambiguity rather than clarity. The multi-line prose format is serviceable but not tightly front-loaded.

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 must describe returns, and it does so fully for both in-progress and finished states. It also links to the initiating tool and the analogous progress tool, leaving only input-parameter provenance and failure modes unaddressed.

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?

There is a single required `task_id` with 0% schema description coverage, so the description carries the load. Saying the run was 'started with start_walkforward' hints that task_id comes from that call's response, but the description never states this mapping explicitly or gives any format details.

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 walk-forward') and ties it explicitly to `start_walkforward`, so an agent can pair the two. It doesn't name the other progress-polling siblings (get_backtest_progress, get_primitives_run_progress) as alternatives, so differentiation is only partial.

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?

The description implies polling usage by describing how progress changes and what appears once finished, and it references `get_primitives_run_progress` as an analogue for circuit-based rules. It never says when to pick this tool over `list_my_running_tasks` or the other scan/backtest progress tools, so routing guidance remains inferred.

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