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

mcp-server-qidi

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Emergency stop

qidi_emergency_stop
Destructive

Immediately halt the QIDI printer by stopping heaters and motors during a real emergency such as a crash, smoke, or filament blob; a firmware restart is required afterward.

Instructions

Immediately halt the printer (M112): heaters and motors stop and the job is lost. Only for a real problem (spaghetti over the hotend, crash, smoke). Afterwards the printer needs qidi_firmware_restart.

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": {
      "reason": "<reason>"
    },
    "name": "qidi_emergency_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhat is wrong — kept in the audit log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description goes beyond that by specifying what is destroyed (the job is lost) and that heaters and motors stop. It also discloses the necessary remediation step (firmware restart), which no annotation conveys. It does not say what state the printer is left in or what permissions are required, keeping it from a 5.

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 and its severity, followed by the trigger condition and the recovery step. Every sentence contributes information an agent needs before invoking a destructive halt.

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 one-parameter destructive tool with full annotation coverage and no output schema, the description supplies the action, the consequence, the trigger condition, and the recovery path. Only the post-call printer state and return value are left unstated, a minor gap given the annotations.

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% for the single 'reason' parameter, including the audit-log note, so the schema carries the meaning. The description adds no format or content guidance for the reason string (e.g., what level of detail helps the audit log), so the baseline 3 applies.

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?

States a specific verb and resource with unusual precision — 'Immediately halt the printer (M112)' — and adds the consequence 'heaters and motors stop and the job is lost' so the agent grasps the severity instantly. It never names the sibling it is contrasted with (qidi_cancel_print or qidi_pause_print), leaving the differentiation implicit.

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?

'Only for a real problem' with concrete triggers (spaghetti over the hotend, crash, smoke) gives a clear when-to-use rule and implicitly excludes routine stops. It also names the required follow-up tool, qidi_firmware_restart, which is genuinely actionable sequencing information; only explicit naming of the softer alternative is missing.

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