Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

plan_supports

Read-only

Plan support strategy for a single 3D part: decide what the slicer should do under each overhang and why, including material and interface choices.

Instructions

Plan the supports for one part: what the slicer should do under each overhang, and why.

Needs Kiln Pro.

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": {
      "input_path": "<input_path>"
    },
    "name": "plan_supports"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoThe filament family the part prints in (``PLA``, ``PETG``, ``ABS``, ``ASA``, ``PA``, ``TPU``, ``PC``). Default: "PLA".
input_pathYesThe model (STL, OBJ, 3MF, or a STEP file, which is analysed as Kiln's mesh of it).
printer_idNoThe printer, for the nozzle on record.
layer_heightNoThe layer height the part will print at, mm. Default: 0.2.
nozzle_diameterNoThe nozzle size, when stated; else the nozzle on record for ``printer_id``, else the printer's own setting.
second_materialNoA support material loaded in a second slot (``PVA``, ``BVOH``, ``HIPS``, or a material that does not bond to the part's), for a dissolving or peeling interface.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / input_path / description
      Added value: +"The model (STL, OBJ, 3MF, or a STEP file, which is analysed as Kiln's mesh of it)."
    • changedInput schema / properties / layer_height / description
      Previous value: -"Default: 0.2."New value: +"The layer height the part will print at, mm. Default: 0.2."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"The filament family the part prints in (``PLA``, ``PETG``, ``ABS``, ``ASA``, ``PA``, ``TPU``, ``PC``). Default: \"PLA\"."
    • addedInput schema / properties / nozzle_diameter / description
      Added value: +"The nozzle size, when stated; else the nozzle on record for ``printer_id``, else the printer's own setting."
    • addedInput schema / properties / printer_id / description
      Added value: +"The printer, for the nozzle on record."
    • addedInput schema / properties / second_material / description
      Added value: +"A support material loaded in a second slot (``PVA``, ``BVOH``, ``HIPS``, or a material that does not bond to the part's), for a dissolving or peeling interface."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the non-obvious constraint that Kiln Pro is required and characterises the return as a reasoned plan ("what the slicer should do ... and why"), which is context the structured fields do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the purpose and the output shape front-loaded and the prerequisite placed last as a short qualifier. Nothing is redundant.

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 read-only planning tool with full schema coverage and no output schema, the description covers purpose, output nature, and the tier prerequisite. It could say more about how the plan is returned or consumed, but nothing an agent needs in order to invoke it correctly is missing.

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 including material, layer_height, nozzle_diameter and second_material is already documented in the schema. The description adds only the "one part" scoping hint and no detail on defaults, units, or precedence rules, so baseline 3 applies.

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?

States a specific verb and resource ("Plan the supports for one part") and clarifies the output is a per-overhang strategy with rationale. That distinguishes it from the pure-number siblings estimate_supports and estimate_support_material, though it never names them explicitly.

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?

"Needs Kiln Pro" gives a real gating prerequisite, which is more than most descriptions offer. But it never says when to choose this over estimate_supports/estimate_support_material or what stage of a workflow it belongs to, so the when-to-use guidance 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