Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

emergency_stop

Destructive

Triggers an immediate stop on one or all 3D printers during genuine safety emergencies, sending the stop command each printer accepts rather than a graceful cancel.

Instructions

Trigger an emergency stop on one or all printers.

Sends the strongest stop each printer accepts: Moonraker's emergency-stop
endpoint; ``M112`` on OctoPrint, Duet and USB-serial printers; a cancel
plus ``M112`` on Elegoo; a job cancel on Prusa Link, which has no raw
G-code endpoint; and on Bambu the print-stop command, a heater cut and
``M112``.  Creality printers use whichever of these their connection is.
Unlike ``cancel_print``, this is not meant to allow a graceful cooldown.

Only the Bambu stop is read back: its ``success`` means the printer
reported the job ended.  On every other printer ``success`` means the
stop command was delivered, not that anything was observed.  ``success``
is False for any printer whose stop failed or could not be confirmed;
when stopping all printers, ``not_confirmed_stopped`` lists each one with
the reason.  Tell the user to stop those at the machine; calling this tool
again for them is safe.

Use only in genuine safety emergencies (thermal runaway, collision,
spaghetti failure threatening the hotend, etc.).

WARNING: After an emergency stop the printer typically requires a
power cycle or firmware restart before it can print again.

Args:
    printer_name: Specific printer to stop. If None, stops ALL printers.
    reason: Reason code, one of ``user_request`` (default),
        ``thermal_runaway``, ``collision_detected``, ``material_jam``,
        ``power_anomaly``, ``software_fault``, ``interlock_breach``,
        ``agent_request``; any other value is refused.
    source: Trigger source label for audit context.
    note: Optional operator note.

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

Input Schema

NameRequiredDescriptionDefault
noteNoOptional operator note.
reasonNoReason code, one of ``user_request`` (default), ``thermal_runaway``, ``collision_detected``, ``material_jam``, ``power_anomaly``, ``software_fault``, ``interlock_breach``, ``agent_request``; any other value is refused. Default: "user_request".
sourceNoTrigger source label for audit context. Default: "mcp".
printer_nameNoSpecific printer to stop. If None, stops ALL printers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / note / description
      Added value: +"Optional operator note."
    • addedInput schema / properties / printer_name / description
      Added value: +"Specific printer to stop. If None, stops ALL printers."
    • changedInput schema / properties / reason / description
      Previous value: -"Default: \"user_request\"."New value: +"Reason code, one of ``user_request`` (default), ``thermal_runaway``, ``collision_detected``, ``material_jam``, ``power_anomaly``, ``software_fault``, ``interlock_breach``, ``agent_request``; any other value is refused. Default: \"user_request\"."
    • changedInput schema / properties / source / description
      Previous value: -"Default: \"mcp\"."New value: +"Trigger source label for audit context. Default: \"mcp\"."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / note / default
      Removed value: -null
    • removedInput schema / properties / printer_name / default
      Removed value: -null
    • removedInput schema / properties / reason / default
      Removed value: -"user_request"
    • addedInput schema / properties / reason / description
      Added value: +"Default: \"user_request\"."
    • removedInput schema / properties / source / default
      Removed value: -"mcp"
    • addedInput schema / properties / source / description
      Added value: +"Default: \"mcp\"."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: it documents per-firmware stop mechanisms (Moonraker endpoint, M112, cancel+M112, Bambu print-stop plus heater cut), which is real behavioral context an agent cannot get from destructiveHint=true. It also discloses the crucial asymmetry that `success` means 'delivered' on most printers but 'observed job end' only on Bambu. The remaining gap is permissions/auth requirements and rate/queue effects, which stay unstated.

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 the action and the cancel_print contrast, then the per-vendor mechanics, then the safety caveat. The vendor enumeration is long but each clause carries distinct behavioral information rather than filler. The Args block duplicates the schema and is the one section that does not earn its space.

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?

No output schema exists, yet the description fully explains the return contract: what `success` means per vendor, that it is False on failure or non-confirmation, and that `not_confirmed_stopped` enumerates the reason per printer. It also warns that a power cycle or firmware restart is typically required afterward, which is essential for an agent deciding next steps.

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 the baseline is 3. The Args block largely restates the schema text for printer_name, reason, source and note, adding only the phrase that unknown reason codes are refused (also present in the schema). No extra syntax, interactions, or defaults beyond what structured fields already carry.

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?

First sentence states a specific verb and resource ('Trigger an emergency stop on one or all printers'), including the scope (single vs. all). It explicitly distinguishes itself from the sibling 'cancel_print' as an ungraceful, emergency-only stop. An agent can route between the two without opening either schema.

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?

Names the alternative ('cancel_print') and the condition that separates them: this is not for a graceful cooldown. It also gives the when-to-use trigger list (thermal runaway, collision, spaghetti failure threatening the hotend) and the when-not implied by 'only in genuine safety emergencies.' It even tells the agent what to do on partial failure: instruct the user to stop at the machine, and that re-calling is safe.

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