Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

clear_emergency_stop

Destructive

Acknowledge and clear a 3D printer's emergency stop latch with a required note, after checking emergency status to confirm safety interlocks allow reset.

Instructions

Acknowledge and clear a printer's emergency stop latch.

This is a safety-critical operation.  The latch may be blocked from
clearing if critical interlocks are still active (e.g. thermal sensor
failure).  Call ``emergency_status()`` first to check whether clearing
is possible.

:param printer_name: Printer whose latch to clear.
:param acknowledgement_note: Free-text note explaining why the e-stop is
    being cleared (required -- cannot be empty).
:param acknowledged_by: Identity of the person or system clearing the
    latch (default ``"operator"``).

:returns: Updated latch state, or an error if critical interlocks prevent
    clearing.

See also: ``emergency_status()``, ``emergency_stop()``.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "printer_name": "<printer_name>",
      "acknowledgement_note": "<acknowledgement_note>"
    },
    "name": "clear_emergency_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_nameYesPrinter whose latch to clear.
acknowledged_byNoIdentity of the person or system clearing the latch (default ``"operator"``). Default: "operator".
acknowledgement_noteYesFree-text note explaining why the e-stop is being cleared (required -- cannot be empty).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / acknowledged_by / description
      Previous value: -"Default: \"operator\"."New value: +"Identity of the person or system clearing the latch (default ``\"operator\"``). Default: \"operator\"."
    • addedInput schema / properties / acknowledgement_note / description
      Added value: +"Free-text note explaining why the e-stop is being cleared (required -- cannot be empty)."
    • addedInput schema / properties / printer_name / description
      Added value: +"Printer whose latch to clear."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / acknowledged_by / default
      Removed value: -"operator"
    • addedInput schema / properties / acknowledged_by / description
      Added value: +"Default: \"operator\"."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, destructive mutation, but the description adds real value: it is safety-critical, clearing can be refused while interlocks are active, and an error is returned in that case. It stops short of saying what happens to the printer's operating state after the latch is cleared.

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?

The purpose and safety warning are front-loaded, and the rest is organized as parameter and return notes. The reST :param:/:returns: block largely duplicates the input schema, which is mild waste but keeps the doc self-contained.

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?

For a destructive, safety-critical mutation with no output schema, the definition covers the prerequisite check, the failure mode, and the shape of the return value. It could say more about post-clear printer state or authorization expectations, but nothing an agent needs in order to call it 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%, so all three parameters are already documented with the same wording the description repeats (including the 'required -- cannot be empty' note and the 'operator' default). The description adds no syntax, format, or validation detail beyond the schema, so the baseline of 3 applies.

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 line names a specific verb and resource ('Acknowledge and clear a printer's emergency stop latch') and the 'See also' line points at the two related siblings, emergency_status() and emergency_stop(), so an agent can place it without opening other schemas.

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 states the precondition explicitly: call emergency_status() first to check whether clearing is possible, and it explains the blocking condition (active critical interlocks such as a thermal sensor failure). That is a concrete when-to-use and when-not-to-use rule naming the alternative tool.

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