Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

by ProductOfAmerica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_3d

Idempotent

Convert KiCad PCB files to 3D models in STEP, STL, or GLB format, or render a PNG image of the PCB from any side.

Instructions

Export PCB 3D model or render 3D view to image.

`render` fills width, height and side; the mesh formats leave them unset.

Args:
    format: Output format - "step", "stl", "glb", or "render" (PNG image)
    pcb_path: Path to .kicad_pcb file. Optional; omit to use the configured default.
    output_dir: Output directory. Optional; omit to use the configured default.
    width: Image width in pixels (render only)
    height: Image height in pixels (render only)
    side: View side: top, bottom, left, right, front, back (render only)
    quality: Render quality: basic, high (render only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNotop
widthNo
formatNostep
heightNo
qualityNobasic
pcb_pathNo
output_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
sideNo
widthNo
formatYes
heightNo
size_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.1
    • addedInput schema / properties / format / enum
      Added value: +[
+  "step",
+  "stl",
+  "glb",
+  "render"
+]
  2. Changed11 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"
-  },
-  "RenderExportResult": {
-    "properties": {
-      "format": {
-        "title": "Format",
-        "type": "string"
-      },
-      "height": {
-        "title": "Height",
-        "type": "integer"
-      },
-      "path": {
-        "title": "Path",
-        "type": "string"
-      },
-      "side": {
-        "title": "Side",
-        "type": "string"
-      },
-      "size_bytes": {
-        "title": "Size Bytes",
-        "type": "integer"
-      },
-      "width": {
-        "title": "Width",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "path",
-      "size_bytes",
-      "format",
-      "width",
-      "height",
-      "side"
-    ],
-    "title": "RenderExportResult",
-    "type": "object"
-  }
-}
    • addedOutput schema / description
      Added value: +"`render` fills width, height and side; step, stl and glb do not."
    • addedOutput schema / properties / format
      Added value: +{
+  "title": "Format",
+  "type": "string"
+}
    • addedOutput schema / properties / height
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Height"
+}
    • addedOutput schema / properties / path
      Added value: +{
+  "title": "Path",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/RenderExportResult"
-    },
-    {
-      "$ref": "#/$defs/ExportResult"
-    }
-  ],
-  "title": "Result"
-}
    • addedOutput schema / properties / side
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Side"
+}
    • addedOutput schema / properties / size_bytes
      Added value: +{
+  "title": "Size Bytes",
+  "type": "integer"
+}
    • addedOutput schema / properties / width
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Width"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "path",
+  "format",
+  "size_bytes"
+]
    • changedOutput schema / title
      Previous value: -"export_3dOutput"New value: +"Model3dExportResult"
  3. Addedv0.10.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate idempotent and non-destructive behavior, so the description's main addition is the conditional behavior of parameters (render fills dimensions, mesh formats leave them unset) and the default path behavior for pcb_path/output_dir. It does not disclose potential file overwriting or directory creation, but with annotations covering safety, the added context is adequate.

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 starts with a concise purpose statement, then a clarifying sentence about render vs mesh behavior, followed by an organized Args list. Every line adds information necessary for correct use, and the structure makes it easy to scan.

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

Completeness5/5

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

With 7 parameters, conditional dependencies, and no schema descriptions, the description addresses all required usage details: optional paths with defaults, format choices, and parameter applicability per format. The output schema is available so no return-value explanation is needed. The tool is fully specified for an agent to select and invoke correctly.

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 descriptions are absent (0% coverage), so the description carries full responsibility. It explains each of the 7 parameters, including enum values for format, defaults, and render-only constraints for width/height/side/quality. The note about 'render fills width, height and side; the mesh formats leave them unset' adds crucial conditional semantics beyond the 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?

The description opens with 'Export PCB 3D model or render 3D view to image,' which is a specific verb+resource statement. It clearly distinguishes from sibling export tools like export_schematic or export_pcb by focusing on 3D output. The format enumeration (step, stl, glb, render) further clarifies scope.

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 description provides context that render uses width/height/side/quality while mesh formats ignore them, guiding parameter selection. However, it does not explicitly state when to choose this tool over other export tools, such as export_pcb or export_gerbers. The purpose is clear but no alternatives or exclusions are named.

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