qidi-mcp

chamber_heater

Set a QIDI Max 4 heated chamber target in °C (max 65) or turn it off to enable ABS/ASA/PA printing; heating requires confirmation and reports fan and thermal-protection sensor status.

Instructions

Control the Max4's actively heated chamber: set a target in °C (max 65 by policy), or 0 to turn it off. The chamber is what makes ABS/ASA/PA printing work on this machine. Also reports the chamber circulation fan and the independent thermal-protection sensor. Requires confirm=true to heat.

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

Input Schema

Name	Required	Description	Default
`target`	No
`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

A3.8/5.0

Behavior4/5

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

Annotations only declare the generic safety triad, so the description's added details matter: the 65 °C policy ceiling, the 0-means-off convention, and the confirm=true gate for heating. It does not explain what happens on a rejected or unconfirmed call, which is the main missing behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the action and limit front-loaded and no filler. The closing sentence about the circulation fan and thermal-protection sensor is partly redundant given an output schema exists, but it is short and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the output schema, so the description does not need to explain them. However, for a mutation tool with zero schema description coverage, leaving confirm_token entirely undocumented and not describing failure/confirmation behavior leaves a real hole an agent could trip on.

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 0%, so the description must carry parameter meaning. It handles target well (°C, max 65 by policy, 0 to disable) and mentions confirm, but confirm_token is never mentioned at all and the relationship between confirm and confirm_token is left entirely unexplained.

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 ('Control the Max4's actively heated chamber') and defines the value semantics: target in °C, 0 turns it off. This clearly separates it from the nozzle/bed-oriented set_temperature, though it never names that sibling explicitly.

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 a clear use context ('what makes ABS/ASA/PA printing work on this machine'), which implies when heating is needed, and states the confirm=true prerequisite. It stops short of explicit exclusions or naming alternatives like cooldown or abort_heating for the off/de-energize path.

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

Deploy Server