Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_thermal_posture

Read-only

Checks all registered 3D printers for thermal-runaway protection and flags drifted settings, helping you identify unsafe or changed machines before printing.

Instructions

Every registered machine's thermal-runaway protection, and what drifted (Business).

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

Input Schema

NameRequiredDescriptionDefault
refreshNoRead each reachable machine now (default; machines are read in parallel). ``False`` answers from stored readings only -- no printer traffic. On a plain install the computer attached to the printers reads each Klipper machine before the call either way (one configuration query each) and keeps the history itself; Kiln's servers keep none. Default: true.
printer_namesNoWhich machines. Omit for every registered machine (each physical machine once). A name that is no longer registered reports its last stored reading.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the '(Business)' tier marker and the notion of drift, without explaining what drift means, how it is computed, or what a stale reading implies.

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

Conciseness3/5

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

It is a single short sentence with no padding, which is good, but the terseness comes at the cost of clarity rather than from efficient phrasing. The parenthetical '(Business)' is front-loaded but unexplained.

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

Completeness2/5

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

With no output schema, the description carries the burden of explaining what is returned, and 'what drifted' is too vague to tell an agent what fields or verdicts to expect. For a fleet-wide read tool with two parameters, this leaves the return shape and the meaning of drift undefined.

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 description coverage is 100%, and the refresh and printer_names parameters are documented in detail in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (every registered machine's thermal-runaway protection) and adds a second dimension (what drifted), so the subject is identifiable. But it is a noun phrase with no verb, and it does not distinguish this from fleet-adjacent siblings like fleet_status, fleet_hardware_stops, or safety_status.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. An agent cannot tell from the text whether this is a monitoring read, an audit, or a pre-print safety gate, nor when to prefer it over fleet_status or safety_status.

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