Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

import_external_mesh

Import STL, OBJ, PLY, GLB, glTF, 3MF, or STEP files as a new design version and open an interactive 3D stage to orbit and inspect the result.

Instructions

Import external geometry (STL / OBJ / PLY / GLB / glTF / 3MF / STEP) as a first-class design version. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link). MAKE DOORS: design_session, Kiln's front door for making an object, is not installed here (signed in to Kiln it runs on Kiln's servers). On this install compile_scad IS the make → preview → iterate loop: make it, show the preview, iterate.

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": {
      "design_id": "<design_id>",
      "mesh_path": "<mesh_path>"
    },
    "name": "import_external_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFree-form notes attached to the version. Default: "".
brief_idNoThe saved goal's id from ``design_session``, so this make is recorded against the goal and checked against it. Empty when there is no goal. Default: "".
design_idYesTarget design (created implicitly).
mesh_pathYesPath to the file to import: STL / OBJ / PLY / GLB / glTF / 3MF, or STEP / STP (converted on the way in; ``NO_BACKEND`` with a ``remedy`` when no converter is installed).
branch_nameNoBranch to attach the import to (default ``main``). Created on the fly if absent. Default: "main".
design_nameNoDisplay name; omitted, the ``design_id`` is used.
source_attributionNoWhere the file came from (free text or a link), stored on the version for audit. A file Kiln downloaded or generated needs none: the note Kiln kept when it arrived (marketplace, designer and license, or generator and prompt) fills this in when it is left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • changedInput schema / properties / branch_name / description
      Previous value: -"Default: \"main\"."New value: +"Branch to attach the import to (default ``main``).  Created on the fly if absent. Default: \"main\"."
    • changedInput schema / properties / brief_id / description
      Previous value: -"Default: \"\"."New value: +"The saved goal's id from ``design_session``, so this make is recorded against the goal and checked against it. Empty when there is no goal. Default: \"\"."
    • addedInput schema / properties / design_id / description
      Added value: +"Target design (created implicitly)."
    • addedInput schema / properties / design_name / description
      Added value: +"Display name; omitted, the ``design_id`` is used."
    • addedInput schema / properties / mesh_path / description
      Added value: +"Path to the file to import: STL / OBJ / PLY / GLB / glTF / 3MF, or STEP / STP (converted on the way in; ``NO_BACKEND`` with a ``remedy`` when no converter is installed)."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Free-form notes attached to the version. Default: \"\"."
    • addedInput schema / properties / source_attribution / description
      Added value: +"Where the file came from (free text or a link), stored on the version for audit.  A file Kiln downloaded or generated needs none: the note Kiln kept when it arrived (marketplace, designer and license, or generator and prompt) fills this in when it is left out."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint=false and destructiveHint=false already set, the description still adds real behavioral context: the tool opens an interactive 3D stage, hosted sessions attach a browser stage link, oversized meshes are decimated for the stage, and STEP input triggers conversion or a NO_BACKEND error with a remedy. That is meaningful disclosure beyond the annotations, though it omits whether imported versions can collide with existing branches or be rolled back.

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 first sentence is well front-loaded, but the inline 3D stage behavior is stated twice (in sentence two and again in the dedicated 'INLINE 3D STAGE' paragraph), and the 'MAKE DOORS' discussion is tangential to an import tool. Substantial redundancy and off-topic material dilute the useful content.

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?

For a seven-parameter import with no output schema, the description covers the important post-call behavior (stage renders, decimation, conversion failure modes) and lets the rich schema handle parameter detail. Only minor gaps remain, such as branch defaulting behavior and what happens to an implicitly created design if the import fails.

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 100%, so every parameter is already documented in the schema, and the description adds essentially nothing new about them beyond repeating the supported file formats. Baseline 3 applies because the schema carries the parameter burden.

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 opening sentence gives a specific verb and resource: 'Import external geometry (STL / OBJ / PLY / GLB / glTF / 3MF / STEP) as a first-class design version.' That is unambiguous. It falls short of 5 because it never names the closely related siblings (import_step_file, import_model_parts, import_external_feature), leaving the agent to infer which import path applies when formats overlap.

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 'MAKE DOORS' block explains environment routing (design_session unavailable, compile_scad is the make loop), but that is guidance about creating objects, not about when to choose this import tool over its import siblings. There is no explicit 'use this when / use X instead' statement for the import decision itself, so usage is only implied.

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