Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

by ProductOfAmerica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_ipc2581

Destructive

Export PCB in IPC-2581 format for manufacturing data exchange.

Instructions

Export PCB in IPC-2581 format for manufacturing data exchange.

Args:
    pcb_path: Path to .kicad_pcb file. Optional; omit to use the configured default.
    output: Output file path. Optional; omit to write <board name>.xml to the
        configured output directory, or beside the board when none is configured.
    precision: Numeric precision (default: 3)
    compress: Compress output file
    version: IPC-2581 version (default: "C")
    units: Output units - "mm" or "in"

Input Schema

NameRequiredDescriptionDefault
unitsNomm
outputNo
versionNoC
compressNo
pcb_pathNo
precisionNo

Output Schema

NameRequiredDescriptionDefault
noteNo
pathYes
formatYes
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.1
    • addedOutput schema / properties / note
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Note"
+}
  2. Addedv0.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description usefully explains the write target: '<board name>.xml' to the configured output directory or beside the board when none is configured. It does not explain whether an existing file is overwritten, which is exactly what the destructiveHint implies, nor any permission requirements.

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?

Purpose sentence is front-loaded, the Args block is terse and each line adds information. No filler or repetition of the title.

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 needn't be explained, and all parameters are covered. The remaining gap is what happens on overwrite and whether compression changes the output filename, which matters given destructiveHint=true.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema has no enums, so the description carries the full burden — and does: it documents all six parameters including defaults for precision (3), version ("C"), units ("mm"/"in"), and the fallback semantics of pcb_path and output. This is meaningfully more than the bare schema.

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?

States a specific verb+resource+format: 'Export PCB in IPC-2581 format for manufacturing data exchange.' That format name alone separates it from siblings like export_gerbers, export_pcb, export_3d, export_netlist and export_bom.

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?

Usage is only implied by the format name; there is no explicit statement of when to choose IPC-2581 over the sibling exporters or any prerequisites (e.g. board must be validated/DCR'd). The agent can infer the choice, but nothing is stated.

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

Deploy Server

Other Tools