Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

recommend_settings

Read-only

Recommend 3D print settings from historical successful prints, filtered by printer, material, or file hash. Use it to pick proven temps, speeds, and slicer profiles before slicing.

Instructions

Recommend print settings based on historical successful outcomes.

Queries the learning database for settings that produced successful
prints, filtered by printer, material, and/or file hash.  Returns
aggregated recommendations (most common temps, speeds, slicer profiles)
plus the raw successful settings for agent review.

When kiln-pro is installed AND the user has a calibrated slicer
profile for ``(printer_name, material_type)``, the calibration coach
overlays personally-tuned values (flow rate, max volumetric speed,
pressure advance, retraction distance) on top of the historical
medians.  The response gains a ``calibration_used`` block and an
extra ``rationale`` line per overridden value naming the slicer +
staleness — so the user sees "Using your calibrated flow rate of
0.95 from OrcaSlicer (updated 12 days ago)" instead of the generic
aggregate.  Behavior is unchanged when kiln-pro is not installed
or no calibration is available.

**Note**: Recommendations are advisory.  They do NOT override safety
limits or preflight checks.  Always validate settings against printer
safety profiles before use.

Args:
    printer_name: Filter by printer (e.g. ``"voron-350"``).
    material_type: Filter by material (e.g. ``"PLA"``, ``"PETG"``).
    file_hash: Filter by file hash for exact file matching.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_hashNoFilter by file hash for exact file matching.
printer_nameNoFilter by printer (e.g. ``"voron-350"``).
material_typeNoFilter by material (e.g. ``"PLA"``, ``"PETG"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / file_hash / description
      Added value: +"Filter by file hash for exact file matching."
    • addedInput schema / properties / material_type / description
      Added value: +"Filter by material (e.g. ``\"PLA\"``, ``\"PETG\"``)."
    • addedInput schema / properties / printer_name / description
      Added value: +"Filter by printer (e.g. ``\"voron-350\"``)."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / file_hash / default
      Removed value: -null
    • removedInput schema / properties / material_type / default
      Removed value: -null
    • removedInput schema / properties / printer_name / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/no-destructive/no-open-world, and the description adds substantial behavior beyond them: what is returned (aggregated medians plus raw successful settings), the exact shape of the kiln-pro overlay (`calibration_used` block, per-value `rationale` with slicer and staleness), and that behavior is unchanged without kiln-pro. The advisory-only warning that recommendations do not override safety limits or preflight checks is a genuinely useful disclosure.

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?

Purpose and return semantics are front-loaded, and the kiln-pro paragraph earns its space by explaining a conditional response shape. It is somewhat long for a read-only lookup tool and uses RST double-backtick markup that adds noise, but there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description explains what comes back (aggregates, raw settings, optional calibration block), so an agent knows what to expect. With three optional, fully documented parameters and annotations covering safety, nothing needed to call this 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% and the Args section largely restates the schema descriptions, including the same examples. The one added nuance is that filters combine with 'and/or' and that all are optional, which is mild value over the schema alone; 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?

The first line states a specific verb and resource: recommend print settings from historical successful outcomes, then clarifies the data source (learning database) and filters. That implicitly separates it from inference/prediction siblings like infer_print_settings or predict_print_settings, but no sibling is named explicitly, so it stops short of full differentiation.

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 gives a clear context for use (query history filtered by printer/material/file hash) and states a precondition for the calibration overlay (kiln-pro installed AND a calibrated slicer profile for that printer/material pair). It never states when to prefer an alternative settings tool such as get_optimal_settings, and gives no explicit exclusions.

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