qidi-mcp

wait_for_temperature

Read-onlyIdempotent

Poll a QIDI Max 4 heater until it reaches its target within tolerance or times out, returning temperature trends so you can verify heating progress.

Instructions

Poll until a heater reaches its target (within tolerance) or the timeout expires. Does not change any target — set_temperature does that. Safe to call repeatedly; returns the temperature trend so you can tell whether heating is actually progressing.

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>"
    },
    "name": "wait_for_temperature"
  }
}

Input Schema

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

Annotations already declare readOnlyHint and idempotentHint, so the description's added value is in stating it is 'safe to call repeatedly' and returns a temperature trend so callers can judge whether heating is progressing. That is genuine behavioral context beyond the structured fields, though it does not say what a timeout expiry looks like in the response.

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 core behavior, then the sibling exclusion, then the safety and return note. No filler and nothing buried.

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?

With an output schema present, return values need not be explained, and the trend mention is a bonus. The remaining gap is the null-target default behavior, which an agent needs in order to call it predictably for a 4-parameter tool.

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 the parameter burden and it only partially does: 'within tolerance' and 'timeout expires' gesture at the tolerance and timeout_s parameters without units or defaults. The most consequential gap is 'target' defaulting to null — the description never says that omitting it means waiting on the heater's currently configured target.

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?

Uses a specific verb and resource: 'Poll until a heater reaches its target (within tolerance) or the timeout expires.' It also explicitly distinguishes itself from set_temperature, so an agent can pick the right tool without opening either 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?

'Does not change any target — set_temperature does that' gives a clear contrast case and routes the mutating action to the sibling. It implies the waiting scenario but never states when not to call it (e.g., for cooling or when already at temperature).

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

Deploy Server