Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_printer_health

Read-only

Monitor a 3D printer’s hotend and bed temperature stability, print progress, and unexpected shutdowns to detect temperature drift and failures early.

Instructions

Run a comprehensive health check on a printer.

Monitors hotend/bed temperature stability, print progress, and
detects anomalies like temperature drift or unexpected shutdowns.

Args:
    printer_name: Name of the printer to check.

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": {
      "printer_name": "<printer_name>"
    },
    "name": "check_printer_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_nameYesName of the printer to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_name / description
      Added value: +"Name of the printer to check."
  2. First observedv0.1.0

TDQS

B3.2/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 contributes the scope of inspection (thermal stability, progress, anomaly detection), which is useful, but says nothing about output shape, latency, whether it issues commands to the machine, or how anomalies are reported.

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?

Front-loaded purpose sentence followed by a compact enumeration of what is monitored. The trailing Args block is redundant with the schema but is short enough not to bloat the definition.

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?

A one-parameter read-only check with no output schema should sketch what a caller gets back (status verdict, flagged anomalies, thresholds) since structured fields cannot. The description explains what is inspected but leaves the return contract entirely implicit.

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?

With 100% schema coverage on a single required 'printer_name' field, the schema carries parameter meaning. The description's Args block repeats the schema text verbatim and adds no format examples, naming conventions, or behavior for an unknown printer name.

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 specific verb and resource ('Run a comprehensive health check on a printer') and enumerates the checks performed (hotend/bed temperature stability, print progress, drift, unexpected shutdowns). It does not, however, distinguish itself from near-neighbors such as check_print_health, health_check, printer_status, or the start/stop_printer_health_monitoring pair.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent facing dozens of printer-diagnostics siblings has no signal for choosing this over troubleshoot_printer, check_print_health, or printer_trend_analysis.

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