mcp-server-qidi

Firmware restart

qidi_firmware_restart

Destructive

Restart Klipper firmware to recover from an emergency stop or error/shutdown state; the action is blocked while a print is active or paused.

Instructions

Restart Klipper firmware after an emergency stop or an error/shutdown state. Refused while a job is printing or paused.

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": "qidi_firmware_restart"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds a real behavioral trait not present in the annotations: the call is conditionally refused during an active or paused print, which prevents a wasted call. It does not spell out what state is lost by the restart, which would have been useful given destructiveHint=true.

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, zero filler, with the action and preconditions front-loaded before the refusal caveat. Every clause carries actionable information.

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 zero-parameter, no-output-schema action tool with full annotation coverage, the description supplies purpose, triggering conditions, and a guard condition. The only gap is post-restart behavior (whether firmware comes back online immediately or what the caller should poll afterward), which would round out the picture.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly offers no parameter discussion, avoiding noise.

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 target ('Restart Klipper firmware') plus the exact states that motivate it (emergency stop, error/shutdown). This clearly separates it from siblings like qidi_resume_print, qidi_emergency_stop, and qidi_printer_status, so an agent can pick it without inspecting other schemas.

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?

Explicitly states when to use it ('after an emergency stop or an error/shutdown state') and when it will be rejected ('Refused while a job is printing or paused'). It stops short of naming a sibling alternative for the printing/paused case (e.g. pause/cancel then restart), so the routing guidance is strong but not complete.

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

Deploy Server