Skip to main content
Glama

render

Create PNG previews of PCB boards or schematic pages, including bare-board and angled 3D views, to verify autoplaced and autorouted designs before review.

Instructions

A PNG of the board or one schematic page, as the person sees it; view board: the bare board as made; 3d: with parts as simple shapes, at an angle. Look after autoplace and autoroute, before asking the person.

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": {
      "file": "<file>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoAlso write it, e.g. pics/top.png
fileYesCircuit file
lookNo
pageNo
sideNo
viewNoDefault "pcb"
angleNo
partsNoZoom to these
sinceNoMark all after it
widthNoPixels; default 1024
changeNoMark this change

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries most of the burden, and it does add useful behavioral context about what each view actually depicts. It says nothing about where the image goes, whether a path is returned, size limits, or the optional file write implied by the 'out' parameter.

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?

Two compact sentences with the deliverable front-loaded and no filler. The telegraphic notation ('view board:', '3d:') and the phrase 'Look after autoplace' are compressed to the point of mild ambiguity, which costs a point.

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

Completeness2/5

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

With 11 parameters, a nested look object, three enums, and no output schema, the description explains only the view modes. Page selection, zooming to parts, and the 'since'/'change' diff-marking semantics — the tool's more complex features — go undescribed.

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 description coverage is 64%, so the baseline is 3. The description does add meaning to the 'view' enum by explaining pcb/board/3d, but it leaves side, angle, page, parts, since, change, width, and the nested 'look' object (mask/silk/finish/background) entirely to the schema.

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?

The description states the output ('A PNG') and the target resource ('the board or one schematic page') and disambiguates the view modes: pcb as the person sees it, board as bare board, 3d with parts as simple shapes at an angle. That is enough to separate it from siblings like export_package or fit_board, though the word 'render' itself never appears as a verb.

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?

'Look after autoplace and autoroute, before asking the person' gives real sequencing advice — visualize after auto-layout/routing and before consulting the user. However, no alternatives are named and there is no when-not guidance (e.g., when to prefer export_fabrication or export_html instead of a PNG).

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