qidi-mcp

pause_print

Pause an active QIDI Max 4 print through Moonraker; parks the toolhead and retracts filament. Requires confirm=true and a running print to execute.

Instructions

Pause the running print. On the Max4 this runs QIDI's PAUSE macro, which parks the toolhead and retracts. Requires confirm=true and an active 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": "pause_print"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	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

A3.5/5.0

Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing the physical side effects: the Max4 runs QIDI's PAUSE macro, which parks the toolhead and retracts. It does not say what state the job is left in, whether it is reversible, or what happens on non-Max4 models.

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?

Two short sentences, front-loaded with the action and followed by the model-specific behavior and preconditions. No filler.

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, so return values needn't be explained, and the annotation set covers the safety profile. Still missing for a mutation tool: what confirm_token is for, and why the description claims confirm is required when the schema marks it optional with default false.

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 must carry parameter meaning and it largely doesn't. It says confirm=true is required, which conflicts with the schema (confirm defaults to false and no parameters are required), and confirm_token is never mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: "Pause the running print," with a concrete model-specific mechanism (QIDI PAUSE macro on Max4) that parks and retracts. Sibling names make the pause/resume/cancel split self-evident, so no explicit differentiation is needed, though the description never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states two preconditions (confirm=true, an active print) which is real usage guidance, but gives no when-not-to guidance and does not point at cancel_print or resume_print for the adjacent operations.

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

Deploy Server