Skip to main content
Glama

breadboardhub circuits

Design a circuit

design_circuit

Designs an electronic circuit (and an Arduino sketch, for microcontroller projects) from a plain description, such as "a 9V battery lighting a red LED". The design passes breadboardhub's structural checks, with one corrected attempt if needed. Returns the CircuitJS circuit, any code, the check result, a link that opens it running live, and the parts to buy with supplier links. Takes up to 2 minutes. 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": {
      "description": "<description>"
    },
    "name": "design_circuit"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesWhat to design, in plain words (10 to 1,000 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint=false tells the agent nothing about cost). It discloses the structural-check step with one automatic corrected retry, a latency bound of up to 2 minutes, a daily quota, and that an API token raises it — all decision-relevant behavior an agent cannot get from 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.

Conciseness4/5

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

Front-loaded with the verb and resource, then the guarantee, then the return payload, then the cost/quota caveat. Four dense sentences, no filler; the return-value list is long but each item is a distinct artifact the caller needs to know exists.

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?

No output schema exists, so the description carries the return contract and does so fully: circuit, code, check result, live link, and parts list with supplier links. Latency and quota also covered — nothing an agent needs before calling 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 coverage is 100% and the schema already specifies 10–1,000 characters of plain text, so baseline is 3. The description adds a worked example of what a good "plain description" looks like, which meaningfully guides phrasing beyond the schema.

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?

States a specific verb and resource — designs an electronic circuit plus an Arduino sketch — and anchors it with a concrete input example ("a 9V battery lighting a red LED"). An agent can tell this generative tool apart from check_circuit, simulate_circuit, edit_circuit, and get_design from the wording alone.

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?

Input framing ("from a plain description") and the example imply when the tool applies, but there is no explicit when-not guidance such as using edit_circuit for iterative tweaks or check_circuit for re-validation. Usage is inferable rather than stated.

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