Skip to main content
Glama

show_on_stage

Read-only

Open existing STL, OBJ, 3MF, STEP, or G-code files in Kiln's interactive 3D stage to orbit, zoom, and inspect them before printing—no remaking or importing needed.

Instructions

Open Kiln's interactive 3D stage on a file that already exists.

        The door for "let me see it" when nothing needs making: a mesh
        from an earlier session, a download, or the sliced print file
        about to go to the printer.  Nothing is re-made, re-sliced,
        imported or written.  Free on every install, like the stage.

        What the stage draws (``shows`` says which, in words):

        - An STL, OBJ or 3MF is drawn as itself; a STEP file is drawn
          from Kiln's mesh of it.
        - A sliced ``.gcode.3mf`` is drawn as the model it carries — the
          file going to the printer, in its paint — with the slicer's
          skirt, brim, prime tower and supports under EXTRAS while this
          machine still holds that slice's G-code.
        - A print file with no model of its own (raw G-code, or an
          archive holding only Kiln's 1 mm placeholder) is drawn as the
          mesh this machine sliced it from, and refused, with the
          reason, when there is no record of that mesh.

        Before a print: open the print file here, let the person turn it
        over, then call ``issue_preview_token(file_path, door="stage")``
        for that same file — the panel's own fetch is the evidence the
        gate reads.  On a host that draws no panel, or until a panel has
        fetched since the server started, the result also carries
        ``viewer_url``: hand it over, and use ``door="url"``.  ``shown``
        says which door this result took.

        ``visualize_model`` is the still-picture door: renders to check
        yourself, and the sign-off only when neither this panel nor a
        link is possible.

        A slice result that opened the stage has already drawn its print,
        from the mesh the slicer was handed, and the print gate counts
        that panel's fetch for the print file the slice wrote.  Called on
        that print file right after, this draws the same slice again,
        from the model the file carries.  ``shown.repeat`` says when the
        panel just above already shows what this one draws.

        :param file_path: Path to an STL, OBJ, 3MF, STEP, ``.gcode.3mf``
            or G-code file on this machine.
        :returns: ``stage_mesh_path`` (the file the stage draws),
            ``shows`` and ``message``, plus ``came_from`` for a file a
            generator or a marketplace download brought in; the stage
            adds ``artifact``, ``shown`` and, when the link is the
            stage, ``viewer_url``.

INLINE 3D STAGE: on success this tool opens Kiln's interactive 3D stage — an inline viewer panel the user can orbit, zoom, and turn over — in hosts that render MCP Apps panels (Kiln's hosted connection attaches a browser stage link for hosts that don't). Oversized meshes are decimated automatically for the stage; the PNG preview is the floor, not the whole experience.

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

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to an STL, OBJ, 3MF, STEP, ``.gcode.3mf`` or G-code file on this machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to an STL, OBJ, 3MF, STEP, ``.gcode.3mf`` or G-code file on this machine."
  2. Addedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it explains file-type-specific rendering, automatic decimation for oversized meshes, refusal cases, `viewer_url` fallback behavior, and `shown.repeat`. Its statement that nothing is re-made, re-sliced, imported, or written is consistent with `readOnlyHint=true` and `destructiveHint=false`.

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

Conciseness3/5

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

The purpose is front-loaded and the bulleted rendering rules are helpful, but the description is very long for a one-parameter tool. It repeats the file-type list and includes extra phrasing like 'Free on every install, like the stage' that does not directly help tool selection or invocation.

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?

Given the interactive-stage complexity, the description covers the important context: supported file types, stage versus still-image alternatives, token workflow, fallback links, and return fields despite having no output schema. It is complete enough for an agent to understand outcomes and prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents `file_path` at 100% coverage, and the `:param` text largely repeats it. However, the description adds meaningful semantics: the file must already exist, specific formats render differently, and missing-mesh G-code cases are refused with a reason.

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 a precise verb and resource: opening Kiln's interactive 3D stage on an existing file. It explicitly distinguishes itself from the still-picture sibling `visualize_model`, so an agent can route between them without inspecting both schemas.

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 guidance: viewing an existing mesh, download, or sliced print file when nothing needs making. It also names the alternative `visualize_model` and the exact pre-print workflow with `issue_preview_token`, including the `door="stage"` sequencing.

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