Skip to main content
Glama

edit_circuit

Apply multiple circuit edits in order as one atomic change across connections, pages, parts, pours, holes, drawings, and sheet settings. If one edit is refused, nothing is written; refusal is named.

Instructions

Apply several edits in order as ONE change, each with one key shaped like the tool of that name (connect also takes corners). add_drawing, set_drawing, remove_drawing, add_page, rename_page, remove_page, wire_corners, rename_parts, rename_port, sheet_size, set_pour, set_hole: guide { topic: "writing-circuits" }. One refused edit writes nothing; the answer names it.

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": {
      "file": "<file>",
      "edits": "<edits>"
    },
    "name": "edit_circuit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
editsYes

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?

No annotations are provided, so the description must disclose behavior. It usefully states ordering, atomicity ('ONE change'), and failure semantics ('One refused edit writes nothing; the answer names it'), but it does not discuss permissions, reversibility, or the success response.

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?

Two dense sentences are front-loaded with purpose and end with failure behavior. The embedded key list is compact but awkwardly selective, which slightly reduces clarity.

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

Completeness3/5

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

For a complex batch mutation tool with no annotations or output schema, the description covers the core atomic and failure model. It still leaves gaps around all valid edit keys and success output, and the partial key list weakens completeness.

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?

The schema already defines many nested edit keys. The description adds the important rule that each edit object has exactly one key shaped like a tool name and notes that connect also takes corners, but its list of keys omits many keys present in the schema, such as add_hole, add_pour, set_props, disconnect, and add_instance.

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?

The opening sentence states a specific operation: apply several edits in order as one atomic change. It makes the batch-editing role clear, though it does not explicitly name individual sibling tools as the alternative.

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?

It implies this tool is for batching multiple edits atomically, but it does not state when to prefer it over the individual sibling editing tools or when to avoid it. The guide reference for certain keys is useful but not a usage rule.

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