Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

by ProductOfAmerica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_schematic

Idempotent

Export KiCad schematics to PDF, SVG, or DXF for documentation and sharing. Specify a .kicad_sch file and output directory; SVG creates one file per sheet.

Instructions

Export schematic to PDF, SVG, or DXF format.

pdf and dxf produce one file, so path names it and size_bytes is filled.
svg produces one file per sheet, so path names the directory. files and
count are filled either way.

Args:
    format: Output format - "pdf", "svg", or "dxf"
    schematic_path: Path to .kicad_sch file. Optional; omit to use the configured default.
    output_dir: Directory for output files. Optional; omit to use the configured default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNopdf
output_dirNo
schematic_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
countYes
filesYes
formatYes
size_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.1
    • addedInput schema / properties / format / enum
      Added value: +[
+  "pdf",
+  "svg",
+  "dxf"
+]
  2. Changed10 schema fields changedv0.11.0
    • removedOutput schema / $defs
      Removed value: -{
-  "ExportResult": {
-    "properties": {
-      "format": {
-        "title": "Format",
-        "type": "string"
-      },
-      "path": {
-        "title": "Path",
-        "type": "string"
-      },
-      "size_bytes": {
-        "title": "Size Bytes",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "path",
-      "size_bytes",
-      "format"
-    ],
-    "title": "ExportResult",
-    "type": "object"
-  },
-  "MultiFileExportResult": {
-    "properties": {
-      "count": {
-        "title": "Count",
-        "type": "integer"
-      },
-      "files": {
-        "items": {
-          "type": "string"
-        },
-        "title": "Files",
-        "type": "array"
-      },
-      "format": {
-        "title": "Format",
-        "type": "string"
-      },
-      "path": {
-        "title": "Path",
-        "type": "string"
-      }
-    },
-    "required": [
-      "path",
-      "format",
-      "files",
-      "count"
-    ],
-    "title": "MultiFileExportResult",
-    "type": "object"
-  }
-}
    • addedOutput schema / description
      Added value: +"pdf and dxf name one file and fill size_bytes; svg names a directory."
    • addedOutput schema / properties / count
      Added value: +{
+  "title": "Count",
+  "type": "integer"
+}
    • addedOutput schema / properties / files
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Files",
+  "type": "array"
+}
    • addedOutput schema / properties / format
      Added value: +{
+  "title": "Format",
+  "type": "string"
+}
    • addedOutput schema / properties / path
      Added value: +{
+  "title": "Path",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/ExportResult"
-    },
-    {
-      "$ref": "#/$defs/MultiFileExportResult"
-    }
-  ],
-  "title": "Result"
-}
    • addedOutput schema / properties / size_bytes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Size Bytes"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "path",
+  "format",
+  "files",
+  "count"
+]
    • changedOutput schema / title
      Previous value: -"export_schematicOutput"New value: +"SchematicExportResult"
  3. Addedv0.10.1

TDQS

A4.4/5.0
Behavior4/5

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

The description explains format-specific output behavior: single vs multiple files, path semantics, and filled fields (size_bytes, files, count). It also clarifies optional parameters and defaults. This adds context beyond the annotations without contradicting them.

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 description is well-structured with a clear opening sentence, followed by format-specific behavioral notes, and an Args section. It is somewhat verbose but all content is relevant to invoking the tool correctly.

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?

The description covers the core behaviors and parameter semantics, and the presence of an output schema likely documents return values. It misses potential error scenarios and prerequisites, but for an export tool this is adequate.

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?

The schema parameters have no descriptions (0% coverage), so this description carries the full burden. It explains the meaning of each parameter: format enum values, optional schematic_path and output_dir with defaults. It also explains the impact of format on output structure.

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 states 'Export schematic to PDF, SVG, or DXF format' with a specific verb, resource, and output formats. This clearly distinguishes it from sibling export tools like export_netlist, export_pcb, and export_gerbers.

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

Usage Guidelines4/5

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

It provides clear context for use, mentioning that pdf/dxf produce a single file while svg produces one per sheet, which helps the agent set expectations. However, it does not explicitly compare with alternative tools or state when not to use it.

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