Skip to main content
Glama

export_pcb_3d

Export a KiCad PCB as a STEP 3D model for mechanical CAD, with footprint models and warnings for missing or unreadable 3D files.

Instructions

Export a board as a STEP 3D model with kicad-cli, for mechanical CAD.

The model has the board and the 3D models of its footprints. kicad-cli does not add a 3D model that it cannot find or read: the tool then gives a warning with the footprints and the reason. Tell the user about each such footprint.

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_pcb_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
pcb_pathYesThe .kicad_pcb file.
board_onlyNoTrue gives only the board, with no models of the footprints.
output_pathNoOptional .step or .stp file. Default: <board>.step next to the board.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses what the output contains (board plus footprint models), that unresolvable 3D models are silently omitted with a warning, and that the agent should surface each such footprint to the user. It omits overwrite behavior for an existing output_path and what happens if kicad-cli itself fails, which keeps it below a 5.

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?

Three short sentences: the action and audience first, then output composition, then the failure mode and required agent behavior. Every sentence carries information and nothing is repeated from the schema.

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 no explanation, and the description covers the one non-obvious behavior (missing 3D models producing warnings). The remaining gap is error/overwrite handling, which matters for a tool that writes a file to disk.

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 the schema already documents all three parameters, making 3 the baseline. The description does add one useful gloss by explaining that the default model includes footprint 3D models, which implicitly explains what board_only=true removes, but it adds nothing about output_path semantics.

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 a specific verb and resource (export a board), the exact output artifact (STEP 3D model), the underlying tool (kicad-cli), and the intended consumer (mechanical CAD). That distinguishes it cleanly from siblings like render_pcb or export_gerber without needing to name them.

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 'for mechanical CAD' clause implies the use case but never states when to prefer this over render_pcb or when a STEP export is inappropriate. No exclusions or alternatives are named, so the agent must infer the boundary from the purpose alone.

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