Skip to main content
Glama

resume_after_power_loss

Destructive

Resume a 3D print interrupted by power loss using saved recovery state, with a two-step confirmation before printing restarts from the stopped point.

Instructions

Resume the print that was interrupted by a power loss (QIDI's power-loss recovery, 断电续打). Moonraker rebuilds recovery G-code from its saved state and STARTS PRINTING from where it stopped. Only meaningful when the printer's saved state says a print was interrupted — check get_saved_variables for 'was_interrupted' first. Two-step confirmation, because it begins a real print. QIDI-specific: not available on stock Klipper.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description reinforces why: it 'STARTS PRINTING' and requires 'two-step confirmation, because it begins a real print.' That adds real consequence context beyond the flags. It does not say what happens if the saved state is stale or the resume fails mid-rebuild, which is the remaining behavioral gap.

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 its effect, then prerequisites, then safety rationale, then platform caveat — a logical order with no filler sentences. The single dense paragraph is slightly run-on, but every clause carries information.

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, platform-specific tool, the description covers the precondition, the safety gate, and the platform restriction, and an output schema exists so return values need no explanation. The missing piece is the mechanics of the two-step confirmation flow, which the confirmation wording raises but does not resolve.

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 0%, so the description must carry the burden. It does explain the intent of the two parameters ('Two-step confirmation'), but never states how confirm and confirm_token relate: whether confirm=true yields a token, whether the token expires, or what to pass on the first versus second call.

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 ('Resume the print that was interrupted by a power loss') plus a concrete mechanism ('Moonraker rebuilds recovery G-code from its saved state and STARTS PRINTING from where it stopped'). This clearly separates it from resume_print (pause/resume) and start_print (fresh print) among the siblings.

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?

Gives an explicit precondition and the exact check to perform first: 'check get_saved_variables for was_interrupted' before calling. It also flags platform gating ('QIDI-specific: not available on stock Klipper'). It stops short of explicitly contrasting with resume_print, which is the nearest-looking alternative an agent might wrongly pick.

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