qidi-mcp

control_job_queue

Start or pause a shared 3D printer job queue: start releases queued jobs once the printer is idle, pause holds them to prevent surprise starts. Confirm is required.

Instructions

Start or pause the shared job queue. action='start' releases it so queued jobs begin printing as soon as the printer is idle — that needs the printer lease, since it commits the machine. action='pause' holds them, which is always allowed: preventing surprise starts is the safe direction. Requires confirm=true. Neither affects a job that is already printing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "control_job_queue"
  }
}

Input Schema

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

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real context: 'start' requires the printer lease because it commits the machine, 'pause' is unconditionally permitted, and neither mode disturbs an in-flight print. That is meaningful disclosure beyond the annotations. The claim 'Requires confirm=true' sits awkwardly against a schema where confirm is optional with default false, leaving some ambiguity about enforcement.

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 tight sentences, front-loaded with the action pair, then the per-action consequences and the shared constraint, ending with the scope limit. No filler; each sentence adds a distinct decision-relevant fact.

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?

For a mutating queue-control tool with annotations and an output schema, the description covers the safety profile, lease prerequisite, confirm requirement, and blast radius. Only the unexplained confirm_token keeps it from being fully complete.

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 the action property has no enum, so the description must carry the parameter burden. It does define 'start' and 'pause' semantics and the confirm requirement, but confirm_token is never mentioned anywhere, which is a notable gap for a parameter that looks security-relevant.

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?

States a specific verb pair and resource ('Start or pause the shared job queue') and immediately distinguishes the two modes by their effect: releasing queued jobs for printing vs. holding them. An agent can tell this apart from queue_jobs (which adds jobs) and get_job_queue (which reads state) from the description alone.

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 per-action guidance with the condition for each: 'start' releases jobs to print, 'pause' holds them and is always allowed as the safe direction. It also states an explicit scope limit — neither affects a job already printing. It stops short of naming alternatives (e.g., which sibling to use to enqueue jobs), so not a full 5.

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

Deploy Server