Skip to main content
Glama
Sign In
mcp-server-qidi

mcp-server-qidi

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel print

qidi_cancel_print
Destructive

Cancel a running or paused 3D print by providing the exact job filename; this action is irreversible and discards the print job.

Instructions

Cancel the running or paused print. Cannot be undone: the job is lost. Pass the file name of the running job to confirm which job you mean.

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": {
      "filename": "<filename>"
    },
    "name": "qidi_cancel_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesFile name of the job you intend to cancel, as qidi_printer_status reports it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 goes further by stating the concrete consequence: 'Cannot be undone: the job is lost.' That clarifies what is destroyed (the job itself, not merely the queued entry), which is genuine value beyond the annotation flags. It stops short of describing permissions or what the tool returns on success.

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 short sentences, front-loaded with the action, with the irreversibility warning placed before the parameter instruction. No sentence is redundant.

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 single-parameter destructive action with full annotation coverage and no output schema, the definition supplies what an agent needs: the target state, the irreversibility, and how to identify the job. Only the disambiguation from pause/emergency_stop is left implicit.

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 coverage is 100% and the filename parameter is already documented, including that names come from qidi_printer_status. The description's 'confirm which job you mean' adds a safety framing for why the parameter is required, but that is marginal added meaning over the schema.

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?

The description names a specific verb and resource ('Cancel the running or paused print') and scopes it to jobs that are currently running or paused. It does not, however, distinguish itself from the related siblings qidi_pause_print, qidi_resume_print, or qidi_emergency_stop, so an agent must infer the difference between cancel and emergency stop.

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?

Usage is implied by state ('running or paused print'), which tells the agent this applies to active jobs only. There is no explicit when-not guidance and no mention of alternatives such as qidi_emergency_stop for an immediate halt or qidi_pause_print for a reversible stop, leaving the choice between those siblings unaddressed.

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

Deploy Server

Other Tools