qidi-mcp

load_filament

Destructive

Runs QIDI filament loading in three confirmed stages—heat, push, and purge—to swap or feed filament, with checks between stages and refusal during active prints.

Instructions

Run one stage of QIDI's filament load routine (M604). stage='heat' warms up and parks over the purge chute, stage='push' feeds filament in, stage='purge' extrudes until the old colour is flushed. Run them in that order, checking between stages — this mirrors what the printer's own screen does. 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": "load_filament"
  }
}

Input Schema

Name	Required	Default
`stage`	No	heat
`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?

Goes beyond the destructiveHint/readOnlyHint annotations by disclosing a two-step confirmation flow and rejection while a print is active, plus that it mirrors the printer's own screen routine. It does not state what happens if a stage is skipped or whether the hotend stays heated afterward.

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: purpose and stage meanings first, then ordering, then safety constraints. Every clause carries information an agent needs; nothing is redundant with the schema or annotations.

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 explained, and the description covers the core behavioral contract for a destructive multi-stage operation. The remaining gap is the mechanics of the confirmation token, which the agent must supply correctly to invoke the tool at all.

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% and there are no declared enums, so the description's quoting of 'heat', 'push', and 'purge' as stage values is genuinely valuable. However, it says nothing about hotend_temp (default 250), and only alludes to confirm/confirm_token via 'two-step confirmation' without explaining how to obtain or pass the token.

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?

Names a specific verb and resource ('Run one stage of QIDI's filament load routine (M604)') and breaks the operation into three named stages with distinct effects, so an agent knows exactly what it does. It is clearly distinguishable from siblings like unload_filament or extrude_filament.

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 explicit sequencing guidance — run heat, push, purge 'in that order, checking between stages' — and states a hard precondition ('refused during a print'). It does not explicitly contrast with unload_filament or extrude_filament, so the alternative-routing element is only implicit.

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

Deploy Server