qidi-mcp

set_temperature

Idempotent

Set a 3D printer heater's target temperature for the extruder, bed, or chamber; use 0 to turn it off and confirm=true to apply the change safely.

Instructions

Set a heater's target temperature. heater is 'extruder', 'bed', or 'chamber'; target is °C (0 turns the heater off). Returns immediately — the printer heats in the background; use wait_for_temperature to block until it arrives. Requires confirm=true. Refused if the target is outside the safety envelope, and while a print is running unless the server allows it.

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": {
      "heater": "<heater>",
      "target": "<target>"
    },
    "name": "set_temperature"
  }
}

Input Schema

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

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing immediate-return/background-heating behavior, the confirm requirement, refusal due to safety envelope, and refusal during active prints unless server policy permits. This gives the agent concrete expectations about side effects and failure modes.

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?

The description is three front-loaded sentences with no redundant wording. Each sentence adds operational value: parameter meaning, async behavior/alternative, and safety constraints.

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?

Output schema exists, so return-value explanation is not needed, and the description covers the main behavioral and safety constraints for a mutation tool. The main omission is any explanation of confirm_token, which may matter when handling safety refusals.

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?

With 0% schema description coverage, the description compensates substantially: it defines heater values, target units and the special value 0, and states that confirm=true is required. It leaves confirm_token undocumented, which is a meaningful gap for a safety-confirmation workflow.

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 resource ('Set a heater's target temperature') and enumerates valid heater values, making it distinguishable from siblings like get_temperatures, cooldown, chamber_heater, and wait_for_temperature. An agent can identify the operation 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains that the tool returns immediately and directs the agent to wait_for_temperature when blocking is needed. It also states the confirm=true requirement and the conditions under which the call is refused (outside safety envelope, during a running print unless allowed).

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

Deploy Server