Skip to main content
Glama

circuit_edit

Destructive

Apply atomic, revision-checked batch edits to circuits—add, set, remove, connect, disconnect, or merge nets—with full rollback on invalid edits, then export native.

Instructions

Apply an atomic revision-checked batch: add, set (properties/position), remove, connect, disconnect, merge_nets. Any invalid edit rolls back the entire batch. Export native afterward.

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": {
      "project": "<project>",
      "expected_revision": "<expected_revision>",
      "operations": "<operations>"
    },
    "name": "circuit_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
operationsYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: all-or-nothing atomicity, full-batch rollback on any invalid edit, and revision checking before applying. It does not say what happens on a revision mismatch (error vs. conflict payload), which is the one behavioral gap.

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 short sentences, front-loaded with the core verb and scope, then the rollback guarantee, then the follow-up step. Nothing is repeated from the name or the schema and no sentence is filler.

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?

For a destructive batch mutation with no output schema, the description covers the essentials: atomicity, rollback, revision precondition, and supported operation types. Missing pieces are the error/conflict behavior on stale revision and the operation object schema, but the annotations plus schema constraints (minItems 1, maxItems 1000) fill in some of the surrounding picture.

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

Parameters2/5

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

Schema description coverage is 0% and the operations array is typed only as a generic object, so the description carries the full burden. It names the six edit kinds, which hints at what an operation can express, but never describes the shape of an operation object, what 'set' targets, or the semantics of project and expected_revision beyond the word 'revision-checked'.

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 ('Apply an atomic revision-checked batch') and enumerates the supported edit kinds (add, set, remove, connect, disconnect, merge_nets), which lets an agent distinguish it from single-edit siblings like component_add or connect_pins. It stops short of naming any sibling explicitly, so differentiation is inferred rather than declared.

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?

The trailing 'Export native afterward' gives a real workflow cue for what to do next, and 'batch' implies grouping multiple edits. There is no explicit statement of when to prefer this over live_edit, native_apply, or individual component/pin tools, and no stated preconditions beyond the revision check.

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