Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

calibrate_direct

Destructive

Sends raw calibration commands directly to a printer adapter for bed leveling, vibration, or flow tuning; use only when the printer is idle and not printing.

Instructions

Send calibration commands directly to the printer adapter.

For a full guided calibration pipeline (home + bed level + intelligence
guidance), use ``run_calibrate`` instead. This tool sends raw calibration commands via
MQTT (Bambu) or G-code (OctoPrint/Moonraker) automatically. The printer
must be idle — calibration cannot run during a print.

Available options (printer-specific -- not all printers support all):
- ``"bed_leveling"``: Auto bed mesh probing and Z offset calibration
- ``"vibration"``: Input shaper / vibration compensation tuning
- ``"flow"``: Extrusion flow / first-layer inspection calibration
- ``"all"``: Run all available calibration routines

When no options specified, defaults to bed leveling only.

Bambu printers support all options.  OctoPrint/Moonraker support
``bed_leveling`` and ``vibration``.  Other printers may not support
remote calibration.
:param options: Which routines to run: ``"bed_leveling"``,
    ``"vibration"``, ``"flow"`` or ``"all"``, as a list.  Omitted, bed
    leveling only.

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": "calibrate_direct"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoWhich routines to run: ``"bed_leveling"``, ``"vibration"``, ``"flow"`` or ``"all"``, as a list. Omitted, bed leveling only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / options / description
      Added value: +"Which routines to run: ``\"bed_leveling\"``, ``\"vibration\"``, ``\"flow\"`` or ``\"all\"``, as a list.  Omitted, bed leveling only."
  2. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / options / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the machinery risk is signalled structurally; the description adds real value on top with the idle-only constraint, the transport paths (MQTT for Bambu, G-code for OctoPrint/Moonraker), the default when no options are supplied, and the fact that some printers cannot be calibrated remotely. It does not describe failure modes or how to confirm completion, so not a 5.

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?

Front-loaded with purpose, then the alternative, then the precondition, then option details — a sensible order. It loses a point because the closing ':param options' block restates the schema's own parameter description almost verbatim, which is redundant text in an otherwise tight definition.

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 one optional parameter, no output schema, and annotations covering the safety profile, the description supplies everything essential: what it does, the alternative, prerequisites, per-value meaning, and platform support. Only return/feedback expectations (how the agent learns whether calibration started or failed) are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema description already lists the four accepted values and the bed-leveling default, so much of the param text is duplication. The description does add meaning beyond the schema by mapping which values each printer family supports and noting that unsupported printers may fail, which helps an agent choose the value safely.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb (send) and resource (calibration commands) with the target (printer adapter), then immediately contrasts itself with run_calibrate. An agent can tell the raw-command tool apart from the guided-pipeline sibling from the first two sentences.

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

Usage Guidelines5/5

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

It names the alternative (run_calibrate) and the condition that selects it (full guided home + bed level + intelligence guidance), and states the hard prerequisite that the printer must be idle because calibration cannot run during a print. Suitable printers per option are also spelled out, leaving little 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