Picodev Lab

Push a circuit

push_circuit

Free mode only: replace the circuit in the human's browser (the simulation stops). components: [{type, id, properties, x?, y?}] (the board is not a component), wires: [{id, start: {componentId, pinName}, end: {...}, color?, waypoints?: [{x, y}] (the wire's route, 16 points at most)}], in the shape of the setup sheet's circuit; 40 components, 120 wires, 48 KiB. The editor checks types and pins: read the outcome with read_simulation (circuit, circuit_error). 6 per minute.

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": {
      "components": "<components>",
      "wires": "<wires>"
    },
    "name": "push_circuit"
  }
}

Input Schema

Name	Required	Description	Default
`wires`	Yes
`session`	No
`components`	Yes
`agent_token`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 23, 2026

addedInput schema / properties / agent_token / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / agent_token / default
```
Added value: +null
```
removedInput schema / properties / agent_token / type
```
Removed value: -"string"
```

addedInput schema / properties / session / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / session / default
```
Added value: +null
```
removedInput schema / properties / session / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "session",
-  "agent_token",
-  "components",
-  "wires"
-]New value: +[
+  "components",
+  "wires"
+]

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well past the annotations: it discloses that the running simulation stops, that the payload is validated against component types and pins, that the outcome must be read back via read_simulation (circuit, circuit_error), and that the call is rate limited to 6 per minute. It also caps the payload at 40 components, 120 wires and 48 KiB, which is exactly the operational envelope an agent needs.

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?

Dense but well front-loaded: the mode gate and the destructive-ish side effect ('the simulation stops') come first, then structure, then limits. The mid-sentence 'in the shape of the setup sheet's circuit' is a soft reference that adds little and interrupts the flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description doesn't need to explain return values, and it correctly redirects to read_simulation for the validation result. It's nearly complete; the gap is the two optional auth/session parameters and any hint about whether a session must be open first.

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 0% and the schema types components/wires as bare objects, so the description carries the entire burden — and it does, spelling out {type, id, properties, x?, y?}, the wire shape with start/end/color/waypoints, the 16-waypoint cap, and the caveat that the board is not a component. The session and agent_token parameters get no mention at all, which keeps it off a 5.

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: replace the circuit in the human's browser, and explicitly ties it to Free mode, which is a strong scope statement. It does not, however, distinguish itself from the similarly named push_program or push_to_editor siblings, so an agent must infer that 'circuit' versus 'program' is the dividing line.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Free mode only' is an explicit precondition and a de facto when-not rule, which is more than most tools offer. No alternative tool is named for the non-free-mode case (e.g. push_to_editor), so the routing guidance is incomplete at the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Picodev Lab tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.