Skip to main content
Glama

render_pcb

Generate a 3D image of a KiCad PCB for visual layout review, with configurable camera side, resolution, rotation, and quality.

Instructions

Render a 3D view of a board as an image with kicad-cli (KiCad 9 or later).

The image has the board and the 3D models of the footprints: a footprint with no 3D model has no body in the image. Use the image for a visual review of the layout.

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": "render_pcb"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoThe side of the camera: "top" (default), "bottom", "left", "right", "front" or "back".top
widthNoThe width of the image in pixels (default 1600).
heightNoThe height of the image in pixels (default 900).
rotateNoOptional rotation of the board "X,Y,Z" in degrees, for example "-30,0,25".
qualityNo"basic" (default, fast), "high" (ray tracing, slower), "user" or "job_settings" (the settings of KiCad).basic
pcb_pathYesThe .kicad_pcb file.
output_pathNoOptional image file: .png, or .jpg or .jpeg for a JPEG image. Default: <board>_render_<side>.png next to the board.

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 at all, the description carries the full burden. It does add real context beyond the schema: a minimum KiCad 9 requirement and the important caveat that footprints without 3D models appear bodyless in the output. However, it never states whether the tool writes a file to disk, what it returns (path vs. image data), or how failures surface — significant gaps for an unannotated tool.

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, front-loaded with the action, then the rendering caveat, then the use case. No filler or redundancy; every sentence contributes.

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

Completeness3/5

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

Seven parameters are well covered by the schema, but with no output schema and no annotations the description should say what the call produces or returns — an image path, saved file, or inline image — and it does not. Adequate for invocation, incomplete for understanding the result.

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%, and each parameter including side, width, height, rotate, quality and output_path has its own description, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which lands at the baseline for fully documented schemas.

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?

States a specific verb and resource: 'Render a 3D view of a board as an image with kicad-cli'. The agent knows exactly what is produced. It stops short of distinguishing itself from the sibling export_pcb_3d or render_library_item, so the boundary between 'render' and 'export 3D' is left to inference.

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?

Offers a purpose statement — 'Use the image for a visual review of the layout' — which implies when to reach for it, but gives no explicit exclusions and does not name an alternative tool. Guidance is implied rather than stated.

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