qidi-mcp

unload_filament

Destructive

Heats the QIDI hotend to a specified temperature, then retracts and ejects the loaded filament for safe material changes. Use two-step confirmation; the routine is refused during an active print.

Instructions

Run QIDI's filament unload routine (M603). Heats the hotend to the given temperature, then retracts and ejects the filament. Give a temperature appropriate to the filament currently loaded (e.g. 250 for PLA, 280 for PETG). Two-step confirmation; refused during a print.

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

Input Schema

Name	Required	Description	Default
`confirm`	No
`hotend_temp`	No
`confirm_token`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A4.2/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 adds real context beyond them: heating is a side effect, there is a two-step confirmation gate, and the call is rejected mid-print. It does not explain what happens if the confirmation is incomplete or what state the printer is left in on failure.

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?

Four short sentences, front-loaded with the operation and its mechanism, followed by temperature guidance and the confirmation/refusal caveat. No filler or repetition of the title.

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?

An output schema exists, so return values need not be described. For a destructive thermal operation the description covers the key hazards and the print-state guard, but omits the mechanics of completing the two-step confirmation, which is the main thing an agent can get wrong here.

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 0%, so the description must carry parameter meaning; it does this well for hotend_temp, including filament-specific example values. However, confirm and confirm_token are only alluded to via 'two-step confirmation' with no explanation of the token flow or how a token is obtained, leaving two of three parameters underspecified.

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 description names the exact routine (QIDI filament unload / M603) and states the mechanism: heat hotend, retract, eject. This clearly separates it from siblings such as load_filament, extrude_filament, and clean_nozzle without needing to open a schema.

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?

It gives clear usage context (choose a temperature matching the loaded filament, e.g. 250 PLA / 280 PETG) and an explicit when-not condition: 'refused during a print.' It stops short of naming alternatives like load_filament or extrude_filament, so routing between filament operations still requires inference.

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

Deploy Server