Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_pcb_sync

Synchronize PCB layouts with schematics by updating nets, components, and placement to match design changes, with an option to preview proposed changes before applying.

Instructions

...

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": {
      "path": "<path>",
      "schematic": "<schematic>"
    },
    "name": "schematic_pcb_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
libraryNo ...
optionsNo ...
proposeNo ...
placementNo ...
schematicYes ...
create_netsNo ...
remove_extraNo ...
clear_extra_pad_netsNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. The tool name hints at a mutation that synchronizes a PCB from a schematic, but whether writes occur, whether they are reversible, and what permissions are needed are all unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

The field is an empty placeholder rather than prose, so there is no structure or front-loading to assess. This is under-specification, not conciseness.

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

Completeness1/5

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

For a 9-parameter tool with nested objects, no annotations, and no output schema, the description supplies none of the context an agent needs. The boolean flags (propose, create_nets, remove_extra, clear_extra_pad_nets) strongly suggest destructive and dry-run behavior that should be explained but is not.

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% across all 9 parameters including the nested options and placement objects, so the schema itself documents each parameter. The description adds no meaning beyond it, but per the high-coverage baseline a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a literal placeholder (' ...'), containing no verb, no resource, and no indication of what schematic_pcb_sync does. An agent cannot distinguish it from siblings such as schematic_pcb_diff, schematic_apply, or board_apply on the basis of this text.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. Nothing routes the agent between this tool and the many similarly named schematic_* siblings.

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