Skip to main content
Glama

build_circuit

Opens a window in the chat where a circuit of QuanterLab's lab cards is put together step by step, as the lab's canvas shows it: each card arrives, the wires join, and when it runs every card lights up in turn and the result shows under it. It fits a person's own idea that no ready test (start_test) covers, and a change to a circuit built here before (fresh false). The cards go on with circuit_step and the circuit runs with run_circuit. Each run covers the last year unless the person names a span, three years at the most; a longer test runs in the lab. The circuit is kept as the person's project when it runs, so it opens in the lab as built. A run that takes more than two minutes does not start at once: run_circuit answers with its time and why for the person, and runs with confirm: true after their yes.

    Args:
        name: Optional. A short name for the circuit, in the person's words ("RSI dip on KO, tested forward").
        fresh: Optional. False opens the window on the circuit built here last, to change it and run it again;
            else a new, empty circuit.
    

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

Input Schema

NameRequiredDescriptionDefault
nameNo
freshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description discloses real behavior: a one-year default span capped at three years, persistence of the circuit as the person's project so it opens later in the lab, and a two-minute run threshold where run_circuit returns timing and requires confirm: true. What it does not cover is the window mechanics after opening (whether it blocks, what the agent sees when it returns) — a modest gap for an interactive tool.

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 key facts are front-loaded and the alternative routing comes early, but the opening visual narration (cards arriving, wires joining, cards lighting up in turn) is decorative rather than decision-relevant, and the long run-limit sentence is dense. It is serviceable and never misleading, yet several clauses could be tightened without losing information.

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 two-parameter interactive tool with no output schema, the description covers everything an agent needs to call it correctly: when to pick it over siblings, what the two optional arguments do, the default and maximum time span, what happens to the circuit after a run, and the confirm: true escalation path for long runs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden, and it does: name is a short label in the person's own words with a concrete example, and fresh is explained precisely as false reopening the last circuit built here to change and rerun it versus a new empty circuit. Both optional parameters are given meaning the bare anyOf types do not convey.

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?

The description gives a concrete verb and resource: it opens a chat window where a circuit of lab cards is assembled step by step, cards arrive, wires join, and results show under each card. It explicitly separates this from start_test (for ideas no ready test covers) and from circuit_step/run_circuit, so an agent can place it among its siblings immediately.

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?

It names the exact conditions for use: a person's own idea that no ready test covers, or editing a circuit built here before (fresh false). It also routes follow-up work to circuit_step for adding cards and run_circuit for execution, and states the runtime limit beyond which the lab takes over.

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