Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

make_printable

Converts messy or AI-generated meshes into print-ready solids tuned for your printer bed and material, then opens the fixed model in an interactive inline 3D stage with a preview.

Instructions

Turn any messy / AI-generated / organic mesh into a print-ready solid. 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 2 print-ready fixes 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": "make_printable"
  }
}

Input Schema

NameRequiredDescriptionDefault
bed_x_mmNoBed width (default 256). Default: 256.0.
bed_y_mmNoBed depth (default 256). Default: 256.0.
bed_z_mmNoBed height (default 256). Default: 256.0.
materialNoFilament (e.g. ``"PLA"``, ``"PETG"``) for tuning. Default: "PLA".
design_idNoOptional design to track this under. When given, the printable result is registered as a new version on a branch (``branch_name``) — your ORIGINAL is never overwritten, the printable variant lives on its own branch, and the provenance records every fix + whether a lossy rebuild simplified detail, so you can always go back to the original. Default: "".
nozzle_mmNoNozzle diameter — sets the wall floor. Leave unset for the nozzle Kiln has for ``printer_id`` (or the only printer it knows of), else 0.4; ``nozzle`` in the reply says which.
model_pathYesPath to the mesh (STL / OBJ / 3MF / PLY / GLB).
printer_idNoOptional printer model id for per-printer tuning. Default: "".
branch_nameNoBranch for the printable version (default ``"printable"``). Used only when ``design_id`` is given. Default: "printable".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.5.1
    • changedInput schema / properties / bed_x_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed width (default 256). Default: 256.0."
    • changedInput schema / properties / bed_y_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed depth (default 256). Default: 256.0."
    • changedInput schema / properties / bed_z_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed height (default 256). Default: 256.0."
    • changedInput schema / properties / branch_name / description
      Previous value: -"Default: \"printable\"."New value: +"Branch for the printable version (default ``\"printable\"``).  Used only when ``design_id`` is given. Default: \"printable\"."
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"Optional design to track this under.  When given, the printable result is registered as a new version on a branch (``branch_name``) — your ORIGINAL is never overwritten, the printable variant lives on its own branch, and the provenance records every fix + whether a lossy rebuild simplified detail, so you can always go back to the original. Default: \"\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Filament (e.g. ``\"PLA\"``, ``\"PETG\"``) for tuning. Default: \"PLA\"."
    • addedInput schema / properties / model_path / description
      Added value: +"Path to the mesh (STL / OBJ / 3MF / PLY / GLB)."
    • addedInput schema / properties / nozzle_mm / description
      Added value: +"Nozzle diameter — sets the wall floor.  Leave unset for the nozzle Kiln has for ``printer_id`` (or the only printer it knows of), else 0.4; ``nozzle`` in the reply says which."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Optional printer model id for per-printer tuning. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is a non-readonly but non-destructive, closed-world operation. The description adds useful behavior beyond that: free accounts get two fixes per month, Pro is unlimited, success opens an interactive 3D stage, and oversized meshes are decimated for the stage. It still does not explain the result payload or file-output behavior, but with annotations present this is a solid disclosure.

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 first sentence is strong and front-loaded, and the quota note is useful. However, the inline 3D stage behavior is described twice, once briefly in the first paragraph and again in a dedicated all-caps section, and the closing marketing-style line adds bulk without much decision value.

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 a nine-parameter mutation-style tool with no output schema, the description covers the main purpose, quota, and stage side effect reasonably well. It does not explain what the tool returns, how success is reported, or what happens to the source file, leaving meaningful completeness gaps.

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 the parameter meanings are already carried by the schema. The description adds little per-parameter guidance beyond noting that the input is a mesh and that oversized meshes are decimated for the stage, so the baseline of 3 is appropriate.

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 specific transformation: turning a messy, AI-generated, or organic mesh into a print-ready solid. The purpose is clear, but it does not explicitly distinguish this tool from nearby siblings such as repair_mesh, validate_and_prepare_mesh, or prepare_ai_model_for_print.

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 phrase 'messy / AI-generated / organic mesh' implies the use case, and the quota note adds practical context. However, it gives no explicit when-not guidance and does not name alternatives, so the agent must infer when this tool is preferable to sibling preparation or repair tools.

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