KiCad MCP Pro

Overview Schema Source Related Servers Discussions Admin

pcb_set_stackup

Destructive

Set the active PCB stackup by loading a file-backed profile that defines the layer configuration. Use this to apply a specific layer setup to your board.

Instructions

Set the active board stackup using a file-backed profile.

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": {
      "layers": "<layers>"
    },
    "name": "pcb_set_stackup"
  }
}

Input Schema

Name	Required	Description	Default
`layers`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.2Aug 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotation destructiveHint: true already signals destructive behavior. The description adds the 'file-backed profile' mechanism, but it does not explain side effects, reversibility, or how the layers parameter interacts with the profile. This is minimal extra context beyond the annotation.

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?

The description is a single, front-loaded sentence with no filler. It conveys the core action efficiently.

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

Completeness2/5

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

For a destructive setter with one parameter, the description is too sparse. It does not clarify what 'file-backed profile' means, how the layers argument is used, or what the expected output is (even though an output schema exists). An agent would struggle to construct a valid call without additional context.

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%, so the description must compensate. It does not explain the 'layers' parameter structure or its relationship to the file-backed profile. The only hint is that layers relate to stackup, but no details on how to construct the array or what object properties are expected.

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

Purpose5/5

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

The description clearly states a specific action: 'Set the active board stackup'. This distinguishes it from sibling tools like pcb_get_stackup (retrieval) and si_generate_stackup (generation). The qualifier 'using a file-backed profile' adds context without obscuring the core purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of when to use this over pcb_get_stackup (for reading) or si_generate_stackup (for generating), nor any prerequisites or exclusions. The context signals show many stackup-related siblings, making usage guidance critical but absent.

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

Deploy Server