qidi-mcp

cooldown

Idempotent

Turn off extruder, bed, and chamber heaters in one call to safely end a session or when uncertain of machine state. The box drying heater stays on unless explicitly included.

Instructions

Turn off every heater (extruder, bed, chamber) in one call. Always permitted — this is the safe direction — and the right thing to call when you are unsure of the machine's state or finishing a session. The QIDI Box's own heater (filament drying) is left alone unless also_box_heater=true, so a drying run is not ended by accident.

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

Input Schema

Name	Required	Description	Default
`also_stop_fans`	No
`also_box_heater`	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?

Adds substantive behavior beyond the annotations: the tool is always permitted (no lease/permission gating), acts atomically in one call, and — critically — leaves the QIDI Box drying heater running unless also_box_heater=true, which annotations cannot express. It does not describe behavior for the also_stop_fans flag or what happens if a heater is already off, leaving a small gap.

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 tight sentences, front-loaded with the action, then permission/safety framing, then the one scope caveat that could cause an operational mistake. No filler and no restating of the name.

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 simple two-flag tool with an output schema and rich annotations, this is nearly complete; the box-heater caveat is exactly the kind of context an agent needs. The only omission is any mention of the fans parameter, which an agent might otherwise ignore or misuse.

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%, so the description carries the burden. It explains also_box_heater well, including the default-off rationale, but says nothing about also_stop_fans, leaving one of two parameters undefined anywhere in the definition.

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 and full scope ('Turn off every heater (extruder, bed, chamber) in one call'), which is immediately distinguishable from siblings like set_temperature, chamber_heater, or abort_heating. An agent knows exactly what the tool does and what hardware it covers without opening the schema.

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 clear situational guidance: the right call when unsure of machine state or finishing a session, and notes it is always permitted. It does not explicitly name alternative tools (e.g., set_temperature to zero, abort_heating, chamber_heater) or when not to use it, so it stops short of full when/when-not/alternatives coverage.

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

Deploy Server