Skip to main content
Glama

run_circuit

Runs the circuit built with build_circuit and circuit_step, on the lab's engine, over three years at most, and keeps it as the person's project, so its report's Open in the lab puts the same circuit on the canvas. The window lights up card by card as it runs and the result appears under it. get_primitives_run_progress follows it by its task_id; when the run has finished it answers with the result and report_url, the run's report. Every account runs it within a daily allowance; a refused call does not count. A circuit asked for more than three years runs three, and held says so in one line: a longer test runs in the lab. A run that takes more than two minutes does not start at once: the answer gives its time and why to ask the person with ("This one takes about 25 minutes (20 years of the S&P 500). Run it?"), and the same call with confirm: true starts it after their yes.

    Args:
        name: Optional. The project's name in the person's words, when the circuit has none yet.
        question: Optional. One sentence restating what the run should answer, not the person's message: the
            title of the report, and kept only as that.
        confirm: Optional. True only after the person said yes to the time a first call of this run gave.
    

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

Input Schema

NameRequiredDescriptionDefault
nameNo
confirmNo
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Confirm"
      +}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, openWorldHint=true): discloses a per-account daily allowance, that refused calls do not count, the three-year clamp and its `held` one-liner, the two-minute async threshold with a sample time-estimate message, and the confirm escalation. It also explains the return payload (result, report_url) and the UI behavior (cards lighting up, report's Open in the lab), none of which appears in 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.

Conciseness3/5

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

The core purpose is front-loaded in sentence one, and the Args block is cleanly separated, but the prose is long and several clauses are grammatically tangled ("the answer gives its time and why to ask the person with"), which slows parsing. The allowance, clamp, and confirm rules are each worth stating, but they could be far tighter.

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?

For a non-idempotent, open-world job-launcher with no output schema and no schema descriptions, the description supplies everything an agent needs: prerequisites, the polling companion, the result shape (result, report_url, held), the confirm flow, and the quota behavior. Nothing material about calling it correctly is missing.

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 carries the full load, and it does define all three optional parameters: name (project naming when the circuit has none), question (a one-sentence restatement that becomes the report title and is kept only as that), and confirm (only true after the user accepts a quoted duration). The `confirm` semantics are especially well pinned; the `question` phrasing is slightly convoluted but still conveys the constraint.

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?

Names a specific verb and resource ("Runs the circuit built with build_circuit and circuit_step") and pins the scope ("on the lab's engine, over three years at most"). It also states the persistent side effect (kept as the person's project) and names the sibling that follows the run (get_primitives_run_progress), so an agent can distinguish it from build/step/progress tools without opening a schema.

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 sequencing and alternatives: run after build_circuit/circuit_step, poll with get_primitives_run_progress by task_id, and a concrete confirm protocol (first call returns an estimated time and rationale, the same call with confirm: true starts it after the person agrees). It also states exclusions — anything over three years is held and "a longer test runs in the lab".

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