Kiln

Overview Schema Source Related Servers Discussions Admin

quick_adaptive_plan

Read-only

Generate an adaptive slicing plan from basic model details by combining geometry analysis and plan creation in one call, reducing the need for multiple steps.

Instructions

All-in-one adaptive slicing: analyze geometry + generate plan.

Convenience tool that combines geometry analysis and plan generation
in a single call.  Ideal when you have basic model info and want a
quick adaptive plan without multiple tool calls.

Args:
    material: Material name (PLA, PETG, ABS, etc.).
    model_height_mm: Total model height in mm.
    model_name: Optional model name.
    nozzle_diameter_mm: Nozzle diameter in mm.  Leave unset for the
        nozzle Kiln has for ``printer`` (or the only printer it knows
        of), else 0.4; the reply's ``nozzle`` says which.
    mode: Adaptive strategy — "balanced", "quality_first",
        "speed_first", or "material_optimized".
    printer: Optional printer identifier.
    regions: Optional list of region dicts.  If omitted, a default
        STANDARD region spanning the full height is used.

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": {
      "material": "<material>",
      "model_height_mm": "<model_height_mm>"
    },
    "name": "quick_adaptive_plan"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Adaptive strategy — "balanced", "quality_first", "speed_first", or "material_optimized". Default: "balanced".
`printer`	No	Optional printer identifier.
`regions`	No	Optional list of region dicts. If omitted, a default STANDARD region spanning the full height is used.
`material`	Yes	Material name (PLA, PETG, ABS, etc.).
`model_name`	No	Optional model name. Default: "".
`model_height_mm`	Yes	Total model height in mm.
`nozzle_diameter_mm`	No	Nozzle diameter in mm. Leave unset for the nozzle Kiln has for ``printer`` (or the only printer it knows of), else 0.4; the reply's ``nozzle`` says which.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.5.1Nov 5, 2026

addedInput schema / properties / material / description

Added value: +"Material name (PLA, PETG, ABS, etc.)."

changedInput schema / properties / mode / description

Previous value: -"Default: \"balanced\"."New value: +"Adaptive strategy — \"balanced\", \"quality_first\", \"speed_first\", or \"material_optimized\". Default: \"balanced\"."

addedInput schema / properties / model_height_mm / description
```
Added value: +"Total model height in mm."
```

changedInput schema / properties / model_name / description

Previous value: -"Default: \"\"."New value: +"Optional model name. Default: \"\"."

addedInput schema / properties / nozzle_diameter_mm / description

Added value: +"Nozzle diameter in mm.  Leave unset for the nozzle Kiln has for ``printer`` (or the only printer it knows of), else 0.4; the reply's ``nozzle`` says which."

addedInput schema / properties / printer / description
```
Added value: +"Optional printer identifier."
```

addedInput schema / properties / regions / description

Added value: +"Optional list of region dicts.  If omitted, a default STANDARD region spanning the full height is used."

Changed9 schema fields changedv1.5.0Oct 23, 2026
- removedInput schema / properties / mode / default
```
Removed value: -"balanced"
```
- addedInput schema / properties / mode / description
```
Added value: +"Default: \"balanced\"."
```
- removedInput schema / properties / model_name / default
```
Removed value: -""
```
- addedInput schema / properties / model_name / description
```
Added value: +"Default: \"\"."
```
- addedInput schema / properties / nozzle_diameter_mm / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / nozzle_diameter_mm / default
```
Removed value: -0.4
```
- removedInput schema / properties / nozzle_diameter_mm / type
```
Removed value: -"number"
```
- removedInput schema / properties / printer / default
```
Removed value: -null
```
- removedInput schema / properties / regions / default
```
Removed value: -null
```
First observedv0.1.0Jul 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: what happens when nozzle_diameter_mm is omitted (nozzle Kiln has for the printer, else 0.4, reported back in the reply's 'nozzle'), and that omitting regions produces a default STANDARD region spanning the full height. It stops short of describing what the generated plan contains.

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 two sentences are well front-loaded and do the real work. However, the trailing Args block duplicates schema descriptions almost word for word, adding length without adding information, which dilutes the otherwise tight structure.

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 7-parameter tool with no output schema, the definition covers inputs and default-resolution behavior reasonably well, but it never describes what the returned adaptive plan looks like or how it should be consumed downstream. The only hint about output is the incidental mention of the reply's 'nozzle' field.

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 is already documented, and the Args block in the description largely restates those schema descriptions verbatim, including the nozzle fallback and the regions default. It adds little interpretive meaning beyond the schema, so the baseline of 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?

The description gives a specific verb+resource pair ('All-in-one adaptive slicing: analyze geometry + generate plan') and frames the tool as a convenience combination, so an agent immediately knows it produces an adaptive slicing plan rather than raw geometry data. It does not name the sibling tools it substitutes for (e.g., analyze_model_geometry plus generate_adaptive_slicing_plan), so differentiation from those is inferred rather than stated.

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

Usage Guidelines4/5

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

'Ideal when you have basic model info and want a quick adaptive plan without multiple tool calls' gives a clear triggering condition and contrasts with the multi-call path. There is no explicit when-not-to-use guidance (e.g., when full control over region analysis or overrides is needed, which other siblings such as the standalone plan generator may offer).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server