Skip to main content
Glama

set_polar_cooler

Turn the QIDI Max 4 chamber cooler on or off to keep the chamber cool when printing PLA in a warm environment.

Instructions

Turn the Max4's chamber cooler ('Polar_cooler' — the active chamber air-conditioning) on or off. Used for PLA in a warm chamber, where you want the chamber cooler rather than hotter.

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": {
      "on": "<on>"
    },
    "name": "set_polar_cooler"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare it is a non-read-only, non-destructive, non-idempotent mutation. The description adds that it controls chamber air-conditioning hardware and names the PLA use case, but it does not say whether the setting persists, how it interacts with the chamber heater, or whether it is safe to toggle mid-print.

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?

Two sentences, front-loaded with the action and device, followed by the use case. No redundant wording; slightly more precision about the cooler/heater distinction would improve it.

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?

For a one-parameter boolean switch with an output schema, the description is close to sufficient: the device and purpose are clear. It still omits behavior around state persistence and interaction with the chamber heater, which an agent may need in a warm-chamber scenario.

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 does convey that the single boolean toggles the cooler on versus off, which is adequate for this trivial parameter, but adds no detail about default state or persistence.

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 concrete verb (turn on or off) and the exact resource ('Polar_cooler', the active chamber air-conditioning). It is distinguishable from the sibling chamber_heater by naming the cooler explicitly, though it doesn't directly contrast with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives a use case (PLA in a warm chamber where you want cooling rather than heating), which implies when to use it. It does not give explicit exclusions, prerequisites, or state that chamber_heater is the alternative when you want warmth.

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

Deploy Server

Other Tools