Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

keep_painted_detail

Preserve painted-on detail by converting textures or vertex colors into printable relief, then preview the embossed model in an interactive 3D stage.

Instructions

Keep a model's painted-on detail when it prints. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link).

Free accounts get 3 textures a month; Pro has no monthly limit.

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": {
      "model_path": "<model_path>"
    },
    "name": "keep_painted_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
invertNoRaise the dark marks themselves instead of the bright surroundings (see CHOOSING ``invert``). Default: false.
depth_mmNoMax relief height, additive (default 0.6). Default: 0.6.
design_idNoOptional design to track this under — the result is registered as a new version so the original and the embossed variant both stay in history. Default: "".
model_pathYesThe textured model. GLB/glTF embed their image maps; models that carry vertex colors instead (vertex paint, photogrammetry and marketplace exports — PLY/OBJ) work through those, speckle-smoothed automatically. A plain STL carries neither, and a STEP file carries geometry only — in both cases there is no painted detail to keep, and the tool says so.
output_pathNoWhere to write the STL (default: temp). Default: "".
target_edge_mmNoSurface refinement target (default 1.0 — finer expresses more detail, costs triangles). Default: 1.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • changedInput schema / properties / depth_mm / description
      Previous value: -"Default: 0.6."New value: +"Max relief height, additive (default 0.6). Default: 0.6."
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"Optional design to track this under — the result is registered as a new version so the original and the embossed variant both stay in history. Default: \"\"."
    • changedInput schema / properties / invert / description
      Previous value: -"Default: false."New value: +"Raise the dark marks themselves instead of the bright surroundings (see CHOOSING ``invert``). Default: false."
    • addedInput schema / properties / model_path / description
      Added value: +"The textured model.  GLB/glTF embed their image maps; models that carry vertex colors instead (vertex paint, photogrammetry and marketplace exports — PLY/OBJ) work through those, speckle-smoothed automatically.  A plain STL carries neither, and a STEP file carries geometry only — in both cases there is no painted detail to keep, and the tool says so."
    • changedInput schema / properties / output_path / description
      Previous value: -"Default: \"\"."New value: +"Where to write the STL (default: temp). Default: \"\"."
    • changedInput schema / properties / target_edge_mm / description
      Previous value: -"Default: 1.0."New value: +"Surface refinement target (default 1.0 — finer expresses more detail, costs triangles). Default: 1.0."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world operation. The description adds meaningful behavior beyond that: it opens an inline 3D stage on success, adds a browser-stage link in hosted sessions, decimates oversized meshes for the stage, and documents a monthly texture quota.

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 purpose is front-loaded, but the inline 3D stage behavior is stated once in the opening paragraph and then substantially repeated in the all-caps INLINE 3D STAGE paragraph. The repetition and parenthetical detail make the definition longer than necessary.

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?

The schema is rich and the annotations cover safety, while the description adds stage and quota context. However, it omits the central transformation detail—turning painted detail into printable geometry/STL—and gives no sibling differentiation, leaving meaningful gaps for a complex mesh-printing operation.

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 all six parameters are already documented in detail. The description does not add syntax, constraints, or parameter-specific meaning beyond the schema, which matches the baseline for full coverage.

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 a clear verb and resource: keeping a model's painted-on detail when it prints. It does not explicitly say it generates an STL/relief from texture or vertex color, nor does it distinguish itself from siblings like apply_image_texture or photo_relief.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The quota note is useful operational context, but it does not help an agent choose this tool over texture-application or relief-generation siblings.

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