Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cancel_print_recovery

Destructive

Cancel an active 3D print recovery session by session ID, with an optional reason, to stop an in-progress recovery attempt on your printer.

Instructions

Cancel an active recovery session.

        Args:
            session_id: The session_id to cancel.
            reason: Optional reason for the cancellation.

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": {
      "session_id": "<session_id>"
    },
    "name": "cancel_print_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason for the cancellation. Default: "".
session_idYesThe session_id to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / reason / description
      Previous value: -"Default: \"\"."New value: +"Optional reason for the cancellation. Default: \"\"."
    • addedInput schema / properties / session_id / description
      Added value: +"The session_id to cancel."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / reason / default
      Removed value: -""
    • addedInput schema / properties / reason / description
      Added value: +"Default: \"\"."
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is covered. The description adds the useful qualifier 'active', implying only a running session can be cancelled, but it does not say what happens to the interrupted print, whether the recovery is resumable afterward, or whether the reason is recorded anywhere.

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 sentence is front-loaded and useful, but the Args block is pure duplication of the input schema and could be dropped without loss. Total length is short, so the waste is proportionate but still redundant.

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?

For a simple two-parameter mutation with no output schema, the definition covers the essentials, and annotations carry the safety profile. What is missing is post-cancellation state: whether the session is destroyed or archived, and how to recover or restart it, which matters for a destructive recovery action.

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 both parameters are already documented. The Args block restates the schema text verbatim ('The session_id to cancel', 'Optional reason for the cancellation') and adds no format, provenance, or lookup guidance for obtaining a valid session_id. Baseline 3 applies.

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?

States a specific verb and resource: 'Cancel an active recovery session.' An agent can tell this is the cancellation counterpart to start_print_recovery/complete_print_recovery. It stops short of naming which sibling to use instead when the session is not active.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as complete_print_recovery, start_print_recovery, or get_recovery_session_status. The agent must infer the routing decision from the name alone.

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