Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

auto_multicolor_from_texture

Segments a textured OBJ mesh into discrete color zones for multi-material 3D printing and opens an interactive 3D stage to inspect the result.

Instructions

Segment a textured OBJ mesh into discrete color zones for multi-material printing. 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 multicolor splits 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": {
      "obj_path": "<obj_path>"
    },
    "name": "auto_multicolor_from_texture"
  }
}

Input Schema

NameRequiredDescriptionDefault
n_colorsNoNumber of color zones (= AMS/MMU slot count). Default 4. Default: 4.
obj_pathYesPath to OBJ file with UV coordinates and texture.
output_dirNoOutput directory. Default: auto-generated temp dir. Default: "".
printer_idNoOptional printer ID. Validates n_colors against the AMS/MMU slot count, and names the plate the composed 3MF is placed on so an off-bed split lands on the real bed.
compose_3mfNoCompose a multi-color 3MF from split STLs. Default True. Default: true.
texture_pathNoOverride texture file path (otherwise read from MTL).
min_island_facesNoMinimum faces to keep a color island. Default 3. Default: 3.
min_island_area_mm2NoMinimum area (mm²) for a color island. Default 1.0. Default: 1.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • changedInput schema / properties / compose_3mf / description
      Previous value: -"Default: true."New value: +"Compose a multi-color 3MF from split STLs. Default True. Default: true."
    • changedInput schema / properties / min_island_area_mm2 / description
      Previous value: -"Default: 1.0."New value: +"Minimum area (mm²) for a color island. Default 1.0. Default: 1.0."
    • changedInput schema / properties / min_island_faces / description
      Previous value: -"Default: 3."New value: +"Minimum faces to keep a color island. Default 3. Default: 3."
    • changedInput schema / properties / n_colors / description
      Previous value: -"Default: 4."New value: +"Number of color zones (= AMS/MMU slot count). Default 4. Default: 4."
    • addedInput schema / properties / obj_path / description
      Added value: +"Path to OBJ file with UV coordinates and texture."
    • changedInput schema / properties / output_dir / description
      Previous value: -"Default: \"\"."New value: +"Output directory. Default: auto-generated temp dir. Default: \"\"."
    • addedInput schema / properties / printer_id / description
      Added value: +"Optional printer ID.  Validates n_colors against the AMS/MMU slot count, and names the plate the composed 3MF is placed on so an off-bed split lands on the real bed."
    • addedInput schema / properties / texture_path / description
      Added value: +"Override texture file path (otherwise read from MTL)."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) the description discloses real behavioral traits: a quota (3/month free, unlimited Pro), that the tool opens an interactive 3D stage, and that oversized meshes are decimated automatically. The gap is that it never says what artifacts are written to output_dir (split STLs, composed 3MF, PNG preview), which matters for a non-read-only tool.

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 core purpose is front-loaded, but the ALL-CAPS 'INLINE 3D STAGE' block largely restates the sentence about opening Kiln's interactive stage that already appeared in the first paragraph, and the parenthetical aside about PNG preview is padded. Roughly a third of the text is 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?

With eight parameters, no output schema, and thin annotations, the description should explain what the call produces on disk; it instead spends its space on the viewing experience. It does cover quota, decimation, and the stage behavior, so the agent knows the cost and side effects, but not the resulting files.

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 eight parameters are already documented, and the description adds no format or semantic detail about n_colors, printer_id validation, or the island thresholds. Baseline 3 applies when 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 first sentence gives a specific verb and resource — segment a textured OBJ mesh into discrete color zones for multi-material printing — which is far more concrete than the tool name alone. It does not, however, contrast itself with the closest siblings (auto_color_by_height, auto_color_by_region, segment_mesh_regions), so an agent must infer that texture-driven segmentation is the distinguishing factor.

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?

Usage is implied: you need a UV-mapped, textured OBJ and a multi-material intent, and there is a free-tier budget of three splits per month. There is no explicit statement of when NOT to use it or which sibling to pick when the model has no texture, which is the main routing decision this tool faces.

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