Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

run_calibrate

Destructive

Runs the full 3D printer calibration sequence—homing, bed leveling, and printer-specific guidance—to prepare a registered printer for accurate prints.

Instructions

Full calibration pipeline: home + bed level + printer-specific guidance (recommended).

Higher-level than ``calibrate_direct`` — orchestrates the full sequence and
returns intelligence-based calibration tips. Performs physical calibration
steps (homing, auto bed leveling) and returns printer-specific calibration
guidance from the intelligence database.

Args:
    printer_name: Registered printer name.
    printer_id: Printer model ID for calibration guidance.

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

Input Schema

NameRequiredDescriptionDefault
printer_idNoPrinter model ID for calibration guidance.
printer_nameNoRegistered printer name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / printer_id / description
      Added value: +"Printer model ID for calibration guidance."
    • addedInput schema / properties / printer_name / description
      Added value: +"Registered printer name."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / printer_id / default
      Removed value: -null
    • removedInput schema / properties / printer_name / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, so the mutation profile is known. The description adds genuinely useful context that physical motion occurs (homing, auto bed leveling) and that guidance comes from an intelligence database, but it never explains why this is destructive, what state gets overwritten, or what safety prerequisites (clear bed, no active print) apply before starting.

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 line is well front-loaded, but the description then says the same thing twice ('returns intelligence-based calibration tips' and 'returns printer-specific calibration guidance from the intelligence database'), and the Args block duplicates the schema verbatim. Moderate redundancy for a short definition.

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?

There is no output schema, so the description reasonably describes the return payload, and the annotations carry the safety profile. However, for a physically acting, destructive calibration routine it omits prerequisites, expected duration, and what happens if calibration fails mid-sequence, leaving an agent under-informed before invoking it.

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 baseline is 3. The Args block restates the schema wording verbatim ('Registered printer name', 'Printer model ID for calibration guidance') without adding format, mutual-exclusivity, or fallback behavior between the two optional parameters.

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?

States a specific verb and resource ('full calibration pipeline: home + bed level + printer-specific guidance') and names the sibling it is higher-level than, calibrate_direct. An agent can distinguish this from the other calibration tools without opening the schema.

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?

Marks itself as '(recommended)' and positions itself as the orchestrating higher-level option relative to calibrate_direct. It stops short of stating when calibrate_direct would be preferred instead (e.g., a single axis or a no-tip run), so the routing is suggested rather than fully specified.

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