Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

import_external_feature

Import external feature assets (SCAD, JSON, or mesh) as versioned features for a design or branch, then inspect the result in an interactive 3D stage.

Instructions

Import an external feature asset as a versioned feature. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link).

Needs Kiln Pro.

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": {
      "asset_path": "<asset_path>"
    },
    "name": "import_external_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name for the imported version. Omit it to use a name built from the format and the file's content hash.
notesNoFree-form note stored on the version. Omit it for none. Default: "".
design_idNoId of a design to scope the feature to. Omit it to keep the feature available across all designs.
asset_pathYesPath to the file to import. Its extension picks the format: ``.scad``, ``.json``, or a mesh (``.stl`` / ``.3mf`` / ``.obj``).
feature_idNoId of an existing feature to add this import to as its next version. Omit it (or name an unknown id) to create a new feature with a ``main`` branch.
branch_nameNoFeature branch the new version lands on, created if it does not exist. Defaults to ``main``. Default: "main".
feature_kindNoMesh imports only: ``"custom_scad"`` (default) or ``"part"`` to register a reusable attachable part. Ignored for ``.scad`` and ``.json``, which carry their own kind. Default: "custom_scad".
source_attributionNoWhere the asset came from (free text or a link), stored in the version's metadata for audit. Omit it to record none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • addedInput schema / properties / asset_path / description
      Added value: +"Path to the file to import.  Its extension picks the format: ``.scad``, ``.json``, or a mesh (``.stl`` / ``.3mf`` / ``.obj``)."
    • changedInput schema / properties / branch_name / description
      Previous value: -"Default: \"main\"."New value: +"Feature branch the new version lands on, created if it does not exist.  Defaults to ``main``. Default: \"main\"."
    • addedInput schema / properties / design_id / description
      Added value: +"Id of a design to scope the feature to.  Omit it to keep the feature available across all designs."
    • addedInput schema / properties / feature_id / description
      Added value: +"Id of an existing feature to add this import to as its next version.  Omit it (or name an unknown id) to create a new feature with a ``main`` branch."
    • changedInput schema / properties / feature_kind / description
      Previous value: -"Default: \"custom_scad\"."New value: +"Mesh imports only: ``\"custom_scad\"`` (default) or ``\"part\"`` to register a reusable attachable part.  Ignored for ``.scad`` and ``.json``, which carry their own kind. Default: \"custom_scad\"."
    • addedInput schema / properties / name / description
      Added value: +"Display name for the imported version.  Omit it to use a name built from the format and the file's content hash."
    • changedInput schema / properties / notes / description
      Previous value: -"Default: \"\"."New value: +"Free-form note stored on the version.  Omit it for none. Default: \"\"."
    • addedInput schema / properties / source_attribution / description
      Added value: +"Where the asset came from (free text or a link), stored in the version's metadata for audit.  Omit it to record none."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the description genuinely adds: it discloses that success opens an interactive 3D stage panel, that hosted connections attach a browser stage link, that oversized meshes get decimated automatically, and that a Pro tier is required. That is real behavioral context beyond the annotations. What it does not state is the actual creation side effect (new feature vs. new version) or whether imports are reversible.

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 opening sentence is well front-loaded, but the 'INLINE 3D STAGE' block restates the first paragraph almost verbatim (orbit/zoom panel, hosted browser link) and adds a third sentence about decimation and the PNG preview floor. Roughly a third of the text is redundant repetition rather than new information.

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?

For an 8-parameter mutation with no output schema, the description covers the license gate and the post-success UI behavior but omits the core outcome — whether a new feature with a 'main' branch is created versus a version appended — and says nothing about failure modes or the returned identifier. Adequate but incomplete for the tool's complexity.

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% and every parameter is documented in the schema with defaults and semantics, so the baseline is 3. The description text adds no meaning to any specific parameter — it spends its words on the 3D stage rather than on name, feature_id, branch_name, or feature_kind.

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 gives a specific verb and resource — 'Import an external feature asset as a versioned feature' — which is clearly distinguishable from most siblings. However, it never addresses the closely related import tools in the sibling list (import_external_mesh, import_step_file, import_model_parts), leaving the agent to infer which importer applies to which asset. Clear purpose, but no explicit sibling differentiation.

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?

It states one real prerequisite ('Needs Kiln Pro'), which is useful gating information, and the schema-adjacent text implies the feature_id path adds a version to an existing feature. It gives no explicit guidance on when to choose this over import_external_mesh or import_step_file, and offers no exclusions, 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