Skip to main content
Glama

get_primitives_run_progress

Read-only

Progress of a lab run started with start_primitives_run, start_test, run_circuit, or start_backtest and start_walkforward when they ran the rule as a circuit (their answer's kind is primitives_run).

    Returns `{task_id, status, progress, message, dashboard_url}`; `status` reaches `done` or
    `error`. When the run has finished, the answer also carries `result`, the same summary
    `summarize_workflow` gives: the verdict in words and, under `figures.branches`, each branch
    by its card name with its dates, whether it beat simply holding and its benchmark, and for a
    branch tested over a year or longer its rounded return, Sharpe, worst drop and trades; and
    `report_url`, the report, which the run's circuit card in the chat shows (for a ready test from
    `start_test`, `offers` gives the next runs with their exact calls).
    

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_primitives_run_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the description's job is to add behavior — and it does: status terminates in done or error, a result payload appears only after completion, and report_url/offers semantics are explained. It omits polling cadence or whether progress is monotonic, which keeps it below a 5.

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 content is substantive but the second paragraph is one long run-on sentence stacking result fields, figures.branches details, and offers, which makes it hard to scan. The applicable-starter information is front-loaded, but the return-value block needs breaking up.

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 carries the burden of describing the return shape, and it does so — task_id, status, progress, message, dashboard_url, plus the post-completion result and report_url. It is nearly complete for a poller; only task_id sourcing and error semantics are under-specified.

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 coverage is 0% for the single task_id parameter, and the description never explains where to obtain the task_id (presumably the starter tool's response) or its format. Only one parameter limits the damage, but the description does not compensate for the missing schema documentation.

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 — polling progress of a primitives lab run — and names the exact starter tools that create such runs, plus the condition (answer's kind is primitives_run) that scopes it. This lets an agent distinguish it from sibling progress tools like get_backtest_progress and get_walkforward_progress without opening schemas.

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

Usage Guidelines4/5

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

It clearly says when this tool applies: runs started by start_primitives_run, start_test, run_circuit, start_backtest, or start_walkforward that ran as a circuit. The gating condition is explicit, though it never names the alternative progress tools to use when the answer kind is not primitives_run, leaving that inference to the agent.

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