qidi-mcp

abort_heating

Idempotent

Releases a QIDI heater WAIT that is blocking the print queue when M109/M190/M191 cannot reach target temperature, without emergency stop or firmware restart. Heaters retain their targets.

Instructions

Abort a heater WAIT that is blocking the queue (QIDI's breakheater). If the printer is stuck in M109/M190/M191 waiting to reach a temperature it will never reach, this releases the wait without an emergency stop — so no firmware restart is needed afterwards. Heaters keep their targets; use cooldown to actually turn them off. 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": "abort_heating"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=true), it discloses the key post-conditions: no emergency stop, no firmware restart required, and heater targets are preserved so the action is non-destructive. It also flags a compatibility limitation (QIDI-only, absent on stock Klipper) that annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action, then the failure condition, then the behavioral consequence and the sibling pointer. Nothing is redundant and no sentence is filler.

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?

For a zero-parameter tool with an output schema already present, the description covers everything an agent needs: when it applies, what it does not do, what state is preserved afterwards, and the hardware caveat. No ambiguity remains about safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema leaves nothing to explain; the description correctly avoids inventing parameter detail. Baseline 4 applies for a parameterless tool.

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?

Description opens with a specific verb and resource ("Abort a heater WAIT") and immediately parenthesizes the underlying firmware mechanism ("QIDI's breakheater"). It is clearly distinguishable from cooldown, which it names, and from emergency_stop, which it implicitly contrasts by saying "without an emergency stop".

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 precise trigger condition (stuck in M109/M190/M191 waiting for an unreachable temperature) and gives the alternative ("use cooldown to actually turn them off"). It also states a platform constraint: not available on stock Klipper.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server