Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_apply

Applies a prepared schematic change plan to your KiCad or 立创 EDA Pro project. Pass the plan ID and confirm to commit edits, keeping the schematic in sync with the board.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "schematic_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo ...
optionsNo ...
plan_idYes ...

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 supplied, so the description carries the full burden of behavioral disclosure and provides none. There is no information about whether apply mutates state, whether confirm gates execution, whether the operation is reversible, or what permissions are required.

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 description is an empty placeholder rather than a front-loaded summary; there is no content to be concise about. This is under-specification, not brevity.

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?

A mutating apply tool with a nested options object, a confirm flag, no annotations, and no output schema requires substantial prose context that is entirely absent. An agent cannot safely determine preconditions or effects from the definition alone.

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% for all three parameters (plan_id, confirm, options), so the schema documents the inputs even though the description is silent. Baseline 3 applies because the schema does the work, though the nested options object gets no clarification anywhere in prose.

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 only an ellipsis placeholder (" ..."), so it never states a verb, resource, or effect. Nothing distinguishes schematic_apply from siblings such as board_apply, schematic_propose, or schematic_review.

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 such as schematic_propose or schematic_review. An agent would have to guess entirely from the name.

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