Skip to main content
Glama

breadboardhub circuits

Simulate a circuit

simulate_circuit
Read-only

Runs a CircuitJS circuit in a real circuit simulator until it settles and returns the voltage across and current through each part, plus faults found: a short circuit, nothing flowing, an LED over its current rating, a bulb too dim to light. Takes 10 to 30 seconds. Limited per day; an API token raises the limit.

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": "simulate_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false, but the description adds substantial operational context: a 10-30 second runtime, a daily quota, and that an API token raises that limit. It also discloses what comes back (per-part voltage and current) and the specific failure classes detected (short circuit, no current, LED over rating, bulb too dim), which is exactly the kind of behavior an agent needs before committing to a slow call.

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 dense sentences, front-loaded with the action and immediately followed by what is returned, then timing and quota constraints. Every clause carries information an agent would otherwise have to discover by trial.

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?

With no output schema, the description correctly takes on the job of describing return values and fault reporting, and it also covers latency and rate limits. For a single-parameter tool of this complexity, nothing material is missing.

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?

There is a single parameter at 100% schema coverage, and the schema already explains the CircuitJS export format, the 20,000 character ceiling, and the breadboardhub.com/sim link alternative. The description adds no further meaning about the input, so baseline 3 applies.

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?

"Runs a CircuitJS circuit in a real circuit simulator until it settles" is a specific verb plus resource, and the description names the outputs (voltage/current per part, detected faults). It never explicitly distinguishes itself from the sibling check_circuit, so an agent must infer that this one performs dynamic simulation rather than static validation.

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 by "runs ... until it settles and returns" and by the enumerated fault checks, which tell the agent this is the tool for empirical simulation results. There is no explicit when-not guidance and no sibling is named as an alternative, leaving the choice against check_circuit or design_circuit to inference.

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