Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_material_slicing_profile

Read-only

Retrieve material-specific slicing constraints for adaptive slicing, including layer height limits, bridge/overhang parameters, and fan speeds for a chosen material and nozzle.

Instructions

Get material-specific slicing constraints for adaptive slicing.

Returns layer height limits, bridge/overhang parameters, fan speeds,
and other material-tuned values used by the adaptive slicer.

Args:
    material: Material name — PLA, PETG, ABS, TPU, ASA, Nylon, PC,
        PVA, or HIPS.
    nozzle_diameter_mm: Nozzle diameter in mm (affects layer height
        limits).  Leave unset for the only printer Kiln knows of,
        else 0.4; the reply's ``nozzle`` says which.

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>"
    },
    "name": "get_material_slicing_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesMaterial name — PLA, PETG, ABS, TPU, ASA, Nylon, PC, PVA, or HIPS.
nozzle_diameter_mmNoNozzle diameter in mm (affects layer height limits). Leave unset for the only printer Kiln knows of, else 0.4; the reply's ``nozzle`` says which.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"Material name — PLA, PETG, ABS, TPU, ASA, Nylon, PC, PVA, or HIPS."
    • addedInput schema / properties / nozzle_diameter_mm / description
      Added value: +"Nozzle diameter in mm (affects layer height limits).  Leave unset for the only printer Kiln knows of, else 0.4; the reply's ``nozzle`` says which."
  2. Changed3 schema fields changedv1.5.0
    • 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"
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it enumerates the returned fields (layer height limits, bridge/overhang, fan speeds) despite having no output schema, and it discloses that leaving nozzle_diameter_mm unset silently selects the only known printer and echoes the choice back in the reply's 'nozzle' field.

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 sentence and return-value summary are front-loaded and efficient. The trailing Args section duplicates schema descriptions word-for-word, adding roughly half the text without new information.

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?

With no output schema, the description carries the burden of saying what comes back, and it sketches the categories of returned values well; the default-nozzle convention is also explained. Minor gaps remain, such as units on returned values and behavior for unsupported material names.

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 Args block merely restates the schema text verbatim for both material and nozzle_diameter_mm. It adds no new syntax, validation, or fallback semantics beyond what structured fields already convey, making baseline 3 correct.

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 ('Get material-specific slicing constraints') scoped to adaptive slicing, which separates it from generic lookups like get_material or get_material_properties. It never names a sibling alternative, so differentiation is inferred rather than explicit.

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 'used by the adaptive slicer' implies this is the lookup feeding adaptive slicing workflows, and the nozzle parameter note gives a concrete default rule. However, it never states when to prefer this over get_slicer_profile, list_slicer_profiles, or get_material_properties, leaving the routing decision to inference.

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