Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_slicer_profile

Read-only

Retrieve a printer model's tuned slicer profile, including all INI settings and the recommended slicer, to configure slicing for that printer.

Instructions

Get the full tuned slicer profile for a printer model.

        Returns all INI settings (layer height, speeds, temps, retraction, etc.)
        and the recommended slicer.  A catalogued printer's profile is
        served one printer per call and kept on this computer; a printer
        whose record this install does not hold answers with the generic
        ``default`` profile (``profile.id == "default"``).  Free-tier
        profiles (default, ender3, prusa_mk3s, klipper_generic) are
        available to all users.  Premium profiles require a Kiln Pro license.

        Args:
            printer_id: Printer model identifier (e.g. ``"ender3"``,
                ``"bambu_x1c"``, ``"creality_k1_max"``).

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": {
      "printer_id": "<printer_id>"
    },
    "name": "get_slicer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_idYesPrinter model identifier (e.g. ``"ender3"``, ``"bambu_x1c"``, ``"creality_k1_max"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_id / description
      Added value: +"Printer model identifier (e.g. ``\"ender3\"``, ``\"bambu_x1c\"``, ``\"creality_k1_max\"``)."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so the safety profile is covered; the description adds genuine substance beyond that: the return payload (all INI settings plus recommended slicer), local per-printer serving, the 'default' fallback with profile.id == "default", and license gating. It stops short of describing behavior on an invalid printer_id or any error/retry semantics.

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

Conciseness4/5

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

The key facts — what is returned, the per-printer scope, and the default fallback — are front-loaded before the licensing detail. The trailing Args section duplicates structured schema content and could be dropped without loss.

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 describing the return and does so adequately: full INI settings (layer height, speeds, temps, retraction) plus a recommended slicer, with a documented fallback shape. Minor gaps remain around what the default profile contains relative to a catalogued one.

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 coverage is 100% and the Args block restates the schema's printer_id description verbatim, including the same three examples, so no new meaning is added there. The free-tier profile list hints at valid identifiers but does not clearly confirm they are legal printer_id values, so the baseline 3 for full schema coverage is 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?

The description opens with a specific verb+resource: 'Get the full tuned slicer profile for a printer model,' and states that profiles are served one printer per call, which implicitly separates it from list_slicer_profiles. It does not name any sibling explicitly, so the differentiation is left to inference 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?

It supplies real usage context: which profiles are free-tier (default, ender3, prusa_mk3s, klipper_generic), that premium ones need a Kiln Pro license, and that an uncatalogued printer degrades to the 'default' profile. What it lacks is routing guidance — it never says when to prefer list_slicer_profiles, get_material_slicing_profile, or slice_model instead.

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