Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_temperatures

Read-onlyIdempotent

Read current temperatures, target values, heater power, all sensor readings, and temperature-controlled fan states from a QIDI Max 4 printer to monitor thermal conditions.

Instructions

Current temperature, target, and heater power for every heater, plus all read-only temperature sensors (including the Max4's chamber thermal-protection sensor) and temperature-controlled fans.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine scope information beyond that: it reports every heater, all read-only sensors, the Max4 chamber thermal-protection sensor, and temperature-controlled fans, telling the agent the payload is broader than a single-hotend read.

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?

A single sentence that front-loads the primary data (current temperature and target) and then appends scope qualifiers. No filler, no restatement of the title or annotations.

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?

A low-complexity read with full annotation coverage and an output schema, so return formatting need not be explained. The description fully defines what is in scope; the only minor gap is the absence of any pointer to related tools for history or setpoints.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description does not need to add parameter meaning.

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?

Names the exact resource and the exact data returned: current temperature, target, and heater power per heater, plus read-only sensors and temperature-controlled fans. An agent can clearly distinguish it from mutating siblings like set_temperature and from get_temperature_history. It loses a point only because it never names those siblings to sharpen the contrast.

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?

There is no explicit when-to-use or when-not-to-use statement, but the phrasing 'current temperature' implies a snapshot read rather than historical or setpoint-mutating usage. The agent must infer that get_temperature_history or get_printer_status are alternatives.

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