qidi-mcp

clean_nozzle

Heats the hotend, moves over the purge chute, and wipes the nozzle before a critical first layer; requires confirmation and is refused during an active print.

Instructions

Run QIDI's nozzle-cleaning routine (CLEAR_NOZZLE): heats up, moves over the purge chute and wipes the nozzle. Worth doing before a critical first layer. Requires confirm=true; 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": "clean_nozzle"
  }
}

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/5.0

Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds real behavior beyond that: heating the hotend, travel to the purge chute, a confirmation gate, and refusal while a print is active. The gap is that it never explains the confirm_token mechanism or what the output schema reports, so an agent could hit a policy rejection with no stated remedy.

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 compact clauses with the action front-loaded, followed by the value proposition and the constraints. Every sentence carries information; nothing is padding.

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?

An output schema exists and annotations cover the safety profile, so return values need not be described. However, for an action tool gated by a confirmation/token policy, leaving confirm_token undefined and the temperature override implicit is a meaningful omission relative to the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It explains 'confirm' well ('Requires confirm=true') and hints at the hotend via 'heats up', but 'confirm_token' is never mentioned at all despite being a safety-policy artifact an agent must likely obtain from get_safety_policy, and the caller-configurable hotend_temp is not stated.

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 QIDI's nozzle-cleaning routine (CLEAR_NOZZLE)') and immediately describes the physical sequence (heats up, moves over the purge chute, wipes the nozzle). An agent can distinguish this from sibling maintenance tools like bed_mesh_calibrate or z_tilt_adjust without opening any 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?

Gives a concrete when-to-use signal ('Worth doing before a critical first layer') and a hard exclusion ('refused during a print'), which is exactly the kind of precondition an agent needs. It stops short of a full 5 because it does not route to any alternative when the call is refused (e.g., cancel/wait via get_job_status or pause_print).

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

Deploy Server