KiCad MCP Server (IPC API)

Overview Schema Source Related Servers Discussions Admin

export_gerbers

Export Gerber manufacturing files for PCB fabrication. Specify output path and optional layers to generate production-ready data.

Instructions

Export Gerber manufacturing files.

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": {
      "output_path": "<output_path>"
    },
    "name": "export_gerbers"
  }
}

Input Schema

Name	Required	Description	Default
`output_path`	Yes
`layers`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Export Gerber manufacturing files,' omitting whether the tool overwrites files, requires specific board setup, or has side effects. This is insufficient for an agent to predict the tool's behavior.

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

Conciseness2/5

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

The description is extremely short (4 words), which might seem concise but it omits critical information. Every word should add value; here they state only the obvious purpose without earning their place. A longer, more informative description would be more appropriate.

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?

Given the tool has 2 parameters (one required) and no annotation coverage, the description is inadequate. Although an output schema exists, the description fails to explain the tool's core behavior, parameter usage, or how it fits into the workflow. It is not complete enough for an AI agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 what the 'layers' parameter expects (valid layer names, format, or default behavior). The 'output_path' parameter's required nature is noted in schema but not elaborated. The agent has no clue how to populate the parameters correctly.

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 description clearly states the action ('Export') and the resource ('Gerber manufacturing files'), making the tool's purpose immediately understandable. However, it does not distinguish this from sibling export tools like export_3d or export_pdf beyond the file format name.

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 on when to use this tool versus other export tools (e.g., export_drill, export_pdf). The description lacks any context about prerequisites, output file type, or recommended usage scenarios.

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

Deploy Server