Skip to main content
Glama

export_gerber

Export Gerber and drill files from a KiCad PCB with kicad-cli to prepare fabrication output and return the generated files.

Instructions

Export the Gerber and drill files of a board with kicad-cli, for fabrication.

The tool runs "kicad-cli pcb export gerbers", then "kicad-cli pcb export drill", and gives the files that kicad-cli wrote.

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": {
      "pcb_path": "<pcb_path>"
    },
    "name": "export_gerber"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcb_pathYesThe .kicad_pcb file.
output_dirNoOptional folder of the files. Default: the folder "gerber" next to the board.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the concrete mechanism: it runs 'kicad-cli pcb export gerbers' then 'kicad-cli pcb export drill' and returns the files written. That tells the agent this is a write-to-disk operation and roughly what artifacts appear. It does not say whether existing files in the output directory are overwritten, whether the directory is created if missing, or what happens on failure, which are the details that matter for a file-emitting tool.

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?

The purpose sentence is front-loaded and the second paragraph is short and earns its place by revealing the underlying commands. Slightly redundant phrasing ('gives the files that kicad-cli wrote' after naming the export commands), but no filler.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the two parameters are fully covered. What remains missing is modest: overwrite/creation semantics for output_dir and any error behavior. For a small, focused export tool this is close to complete.

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 coverage is 100%, so both pcb_path and output_dir are already documented, including the 'gerber' default folder. The description adds no format, path-resolution or naming convention details beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Export the Gerber and drill files of a board with kicad-cli, for fabrication.' That resource specificity (Gerber + drill) is enough to separate it from export_bom, export_pcb_3d and the report exporters without needing to name them. It stops short of an explicit sibling contrast, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

The phrase 'for fabrication' implies the context of use, and mentioning kicad-cli implies a KiCad project context, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives. The agent must infer that this is the fabrication-output path rather than the 3D or BOM path.

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