Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

trigger_bed_level

Destructive

Triggers bed leveling or mesh probing on a specified 3D printer by sending G29 or BED_MESH_CALIBRATE, helping correct bed height before printing.

Instructions

Trigger a bed leveling / mesh probe on the printer.

Sends the configured G-code command (G29 or BED_MESH_CALIBRATE)
to the printer.

Args:
    printer_name: Target printer.  Omit for the default printer.

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

Input Schema

NameRequiredDescriptionDefault
printer_nameNoTarget printer. Omit for the default printer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_name / description
      Added value: +"Target printer.  Omit for the default printer."
  2. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / printer_name / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the agent knows this is a state-changing action. The description adds real value by disclosing the mechanism (it emits a configured G-code macro, G29 or BED_MESH_CALIBRATE), which implies physical motion, time cost, and possible overwriting of an existing mesh. It stops short of saying that the existing mesh is replaced, whether the call blocks until probing completes, or what happens if a job is active.

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?

Two sentences front-load the action and mechanism, followed by a short Args block; nothing is padded. The Args line is mildly redundant with the schema but conventional and harmless.

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?

The tool is simple (one optional param, no output schema) and annotations carry the safety profile, so this is close to sufficient. What an agent still needs for a destructive physical action — whether it blocks, whether it disrupts an in-progress job, and how to confirm success (presumably via bed_level_status) — is absent.

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% for the single optional parameter, and the description's Args note is a verbatim restatement of the schema's own 'Target printer. Omit for the default printer.' No naming format, validation behavior, or fallback semantics are added beyond the schema.

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 gives a specific verb plus resource ('Trigger a bed leveling / mesh probe') and even names the underlying G-code commands (G29, BED_MESH_CALIBRATE), so the action is unambiguous. It does not, however, differentiate itself from close siblings such as bed_level_status, calibrate_direct, or run_calibrate, leaving the agent to infer the boundary.

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

Usage Guidelines2/5

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

There is no guidance on when to run this versus checking bed_level_status first or using calibrate_direct, and no stated preconditions (printer idle, axes homed, no active print). Usage is only implied by the verb 'trigger'.

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