Skip to main content
Glama
Sign In

PCBEditor

by com.pcbeditor
OverviewDiscussionsAdmin

Change a board in plain language

edit_board

Applies a change to an existing design, described in plain language: add or replace parts, move or rotate components, change the outline or connectors, re-route nets, add mounting holes, swap footprints. The change is checked and the board re-routed where needed. Returns a job_id; poll get_job.

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": {
      "design_id": "<design_id>",
      "instruction": "<instruction>"
    },
    "name": "edit_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe design to change.
instructionYesThe change, in plain language.

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?

Goes well beyond the annotations: the change is validated/checked, the board is re-routed where needed, and the call is asynchronous, returning a job_id rather than the result. That async-plus-poll contract is the key behavioral fact and is stated plainly, consistent with readOnlyHint=false and idempotentHint=false.

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 verb and resource, with the capability enumeration and the job_id/poll contract in the following sentences. The capability list is somewhat long but each item guards against an agent assuming a narrower scope; no filler sentences.

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 supplies the return contract (job_id, poll get_job) and the processing semantics (check plus re-route). Annotations cover safety flags, so nothing critical is missing for correct invocation.

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?

Schema description coverage is 100%, so both parameters are already documented. The description reinforces that the instruction is free-form plain language, which matters, but adds no format, limits, or examples beyond the schema's 32000-char cap.

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 (applies a change) on a specific resource (an existing design/board) and enumerates the change classes: parts, moves/rotations, outline, connectors, nets, mounting holes, footprints. That scope implicitly separates it from design_board (creation) and route_board, though no sibling is named explicitly.

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?

Makes clear this is for modifying an existing design and directs the agent to poll get_job for the returned job_id, giving concrete follow-up behavior. It stops short of explicitly saying when to prefer design_board or route_board instead.

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

All PCBEditor toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources