Skip to main content
Glama

visualize_model

Read-only

Render PNG stills of any STL, 3MF, OBJ, or SCAD file from up to six angles to inspect a model from all sides after each change and before printing.

Instructions

Still pictures of any 3D file from multiple camera angles — the still door, not the 3D stage.

FOR THE PERSON'S LOOK BEFORE A PRINT, OPEN THE STAGE: ``show_on_stage(file_path)`` puts a file that already exists — a mesh, or the sliced print file — on Kiln's interactive 3D stage, which the print gate asks for first (``issue_preview_token(door="stage")``). These renders are for checking a model yourself. When the user is signed in the result also carries a browser stage link (``viewer_url``), the door for a host that draws no panel.

INSPECTION-ONLY UNLESS THE STAGE DREW IT: the result's ``renderer`` says which look these pixels are. ``stage`` (the stage photographed) and ``stage_paint`` (the stage's look painted) are accepted by ``issue_preview_token(door="png")`` for print sign-off; a raw ``openscad`` render is not — it has no plate and none of the stage's lighting, and a person once approved the wrong colours from one. Use it to inspect, and sign off from the stage, the viewer link, or a stage still.


Universal visualization tool that works with ANY 3D file — STL, 3MF,
OBJ, or SCAD.  Returns PNG images from 6 angles: isometric, front,
right, top, bottom, and back.

**Colored 3MF support:** Multicolor 3MF files (with per-face color
groups from BambuStudio, PrusaSlicer, or procedural textures) are
automatically rendered with per-face colors — no slicer needed to
see what the multicolor print will look like.  Colorless 3MF and
STL/OBJ files render in uniform color via OpenSCAD as before.
Dark models get an adaptive lighter background for visibility.
Each view includes a ``quality_score`` and ``dark_material`` flag.

Use this to check a model from all sides — after each change, and
before printing.

**When to use this vs other preview tools:**
- ``show_on_stage`` — the interactive 3D stage on an existing file; what the person turns over before a print
- ``visualize_model`` — still renders of any file, 6 angles, to check it yourself
- ``preview_generated_model`` — after AI generation, includes bottom check
- ``visualize_model(angles=["isometric"])`` — one angle, quick check

Args:
    file_path: Path to an STL, 3MF, OBJ, or SCAD file.
    angles: Optional subset of angles to render. Valid values:
        ``isometric``, ``front``, ``right``, ``top``, ``bottom``, ``back``.
        Defaults to all 6.
    width: Image width in pixels (default 800).
    height: Image height in pixels (default 600).
    color: Hex color for the model (e.g. ``"#F72323"`` for red).
        Defaults to neutral grey.  Pass the filament color to see
        a realistic preview matching the printed result.
        Ignored for colored 3MF files (per-face colors used instead).

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_path": "<file_path>"
    },
    "name": "visualize_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex color for the model (e.g. ``"#F72323"`` for red). Defaults to neutral grey. Pass the filament color to see a realistic preview matching the printed result. Ignored for colored 3MF files (per-face colors used instead). Default: "".
widthNoImage width in pixels (default 800). Default: 800.
anglesNoOptional subset of angles to render. Valid values: ``isometric``, ``front``, ``right``, ``top``, ``bottom``, ``back``. Defaults to all 6.
heightNoImage height in pixels (default 600). Default: 600.
file_pathYesPath to an STL, 3MF, OBJ, or SCAD file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • addedInput schema / properties / angles / description
      Added value: +"Optional subset of angles to render. Valid values: ``isometric``, ``front``, ``right``, ``top``, ``bottom``, ``back``. Defaults to all 6."
    • changedInput schema / properties / color / description
      Previous value: -"Default: \"\"."New value: +"Hex color for the model (e.g. ``\"#F72323\"`` for red). Defaults to neutral grey.  Pass the filament color to see a realistic preview matching the printed result. Ignored for colored 3MF files (per-face colors used instead). Default: \"\"."
    • addedInput schema / properties / file_path / description
      Added value: +"Path to an STL, 3MF, OBJ, or SCAD file."
    • changedInput schema / properties / height / description
      Previous value: -"Default: 600."New value: +"Image height in pixels (default 600). Default: 600."
    • changedInput schema / properties / width / description
      Previous value: -"Default: 800."New value: +"Image width in pixels (default 800). Default: 800."
  2. Changed7 schema fields changedv1.5.0
    • removedInput schema / properties / angles / default
      Removed value: -null
    • removedInput schema / properties / color / default
      Removed value: -""
    • addedInput schema / properties / color / description
      Added value: +"Default: \"\"."
    • removedInput schema / properties / height / default
      Removed value: -600
    • addedInput schema / properties / height / description
      Added value: +"Default: 600."
    • removedInput schema / properties / width / default
      Removed value: -800
    • addedInput schema / properties / width / description
      Added value: +"Default: 800."
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes well beyond that: colored 3MF per-face rendering, adaptive lighter background for dark models, per-view quality_score and dark_material flags, a renderer field, and an optional viewer_url when signed in. The one significant gap is that it never says how many images/bytes come back or whether renders are cached, though the renderer/door semantics compensate substantially.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The stage-versus-still distinction is stated three times: in the opening paragraphs, again in the 'INSPECTION-ONLY' paragraph, and again in the 'When to use this vs other preview tools' bullets. Formulas like 'the still door' and 'the door for a host that draws no panel' add length without adding decision value, and the 'ANY 3D file — STL, 3MF, OBJ, or SCAD' line duplicates the schema.

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?

There is no output schema, and the description carries the return-value burden well: it names the six angles, describes per-view quality_score and dark_material, explains the renderer values and their sign-off implications, and mentions the optional viewer_url. For a five-parameter render tool this leaves little an agent would need to guess.

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 every parameter is already documented, and the Args block largely restates those descriptions (angle values, width/height defaults, hex color format). It does add intent for color ('Pass the filament color to see a realistic preview matching the printed result') and a workflow idiom for angles ('angles=["isometric"] — one angle, quick check'), but not enough to exceed the baseline.

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 opening line states a specific verb and resource ('Still pictures of any 3D file from multiple camera angles') and immediately contrasts it with the sibling that is most likely to be confused with it ('the still door, not the 3D stage'). The later section names supported formats and the six angles, so an agent can identify this as the render-to-PNG tool without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use and when-not-to-use guidance: 'FOR THE PERSON'S LOOK BEFORE A PRINT, OPEN THE STAGE: show_on_stage(...)', plus a comparison block covering show_on_stage, preview_generated_model, and the single-angle quick check. It also states the exclusions ('INSPECTION-ONLY UNLESS THE STAGE DREW IT'), which is the strongest form of routing guidance.

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