Skip to main content
Glama

circuit_progress

Read-only

For the circuit card only, which calls it while a ready test runs: which of the circuit's cards have run and which one is running, waiting a few seconds for the next one to finish; when the run has finished, the report card's words and figures, its growth chart and the offers to run next. A rule a start tool ran on its module answers with how far it is, then the same.

    Args:
        task_id: The task_id start_test answered with.
        seen: How many cards the card has already shown as run.
        now: The card it shows as running.
    

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": "circuit_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowNo
seenNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly/non-destructive, so the bar is lower, and the description does add that the call waits a few seconds for the next item to finish and returns richer output once the run completes. However these traits are wrapped in obscure phrasing that weakens their reliability as behavioral disclosure.

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

Conciseness2/5

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

The text is a rambling run-on that mixes purpose, return values and parameters behind opaque jargon, plus an Args block that duplicates the schema. It is not bloated in length but is poorly front-loaded and hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 sketch both the in-progress response (cards run/running) and the finished response (text, figures, growth chart, next-step offers). Remaining gaps – error/timeout behavior and the exact shape of 'offers to run next' – keep it at adequate rather than complete.

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 description coverage is 0%, so the description must carry the parameters – and it does explain all three: task_id from start_test's answer, seen as the count already shown as run, and now as the currently running item. The metaphors are odd, but each parameter gets meaning the schema alone does not provide.

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

Purpose3/5

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

The description does identify a progress-polling role – reporting which 'cards' have run and which is running – and ties it to input from start_test. But the heavily metaphorical vocabulary ('circuit card', 'ready test', 'report card's words and figures') makes the verb/resource hard to pin down, and it never explicitly distinguishes itself from the many get_*_progress siblings.

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?

It implies usage after start_test by saying task_id is 'what start_test answered with', which is a useful cue. There is no explicit statement of when not to use it or how it differs from sibling progress tools like run_card_progress or get_backtest_progress.

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