Skip to main content
Glama

breadboardhub circuits

Check a circuit

check_circuit
Read-only

Free and instant. Checks a CircuitJS circuit for structural problems: unknown parts, loose ends, parts with no power source, LEDs with the wrong diode model, labels on top of parts. With "request", also checks it contains the parts asked for (a bulb, an ammeter, a voltmeter, a switch). Returns the problems, the parts list and a link that opens the circuit running live.

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": {
      "circuit": "<circuit>"
    },
    "name": "check_circuit"
  }
}

Input Schema

NameRequiredDescriptionDefault
circuitYesThe circuit: a CircuitJS export (a "$" options line, then one part per line, at most 20,000 characters), or a breadboardhub.com/sim link that carries one.
requestNoOptional: what the circuit is meant to be, in plain words (at most 1,000 characters).

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?

Beyond the annotations (readOnlyHint=true, openWorldHint=false), the description adds two useful facts: the call is 'Free and instant' (cost/latency) and the 'request' mode performs an additional containment check. It also discloses the return payload — problems, parts list, and a live-run link — which matters since there is no output schema.

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

Conciseness5/5

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

Three tight sentences: cost/latency first, then the validation scope, then the optional mode and return shape. The enumerated check list is information-dense and nothing is repeated from the schema.

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 read-only validator with two parameters and no output schema, the description covers purpose, the extra behavior of the optional parameter, and what comes back. An agent has everything needed to decide to call it and to interpret the result.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining what 'request' actually triggers — a containment check for specific parts — and naming example parts (bulb, ammeter, voltmeter, switch). The accepted input forms for 'circuit' are left to the schema, which already handles them well.

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 and resource ('Checks a CircuitJS circuit') and enumerates exactly what is validated: unknown parts, loose ends, unpowered parts, wrong diode models, overlapping labels. That is far more concrete than a restatement of the name, though it never explicitly contrasts itself with simulate_circuit or edit_circuit.

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?

Usage is implied rather than stated: it is a validation step you would run before simulating or editing, and the 'request' sentence says when the optional parameter applies. There is no explicit when-not-to-use and no sibling is named as an alternative, so the agent must infer placement in the workflow.

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