Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

start_printer_health_monitoring

Start continuous background health monitoring for a printer.

Instructions

Start continuous background health monitoring for a printer.

Runs periodic checks covering connectivity, temperature stability,
print job health (layer progress stalls, error codes), and active
error detection.  Alerts are generated when anomalies are found.

Kiln keeps a live watch on as many machines at once as your plan
runs — one on Free and Pro.  Checking a printer yourself is not a
watch and is never limited: ``printer_status``, ``monitor_print``
and ``printer_snapshot`` answer for any machine at any tier, and so
does stopping one.

:param printer_name: Printer to monitor.
:param interval_seconds: Seconds between health checks (default 30).

See also: ``stop_printer_health_monitoring()``,
``check_printer_health()``, ``printer_status()``.

Input Schema

NameRequiredDescriptionDefault
printer_nameYes
interval_secondsNoDefault: 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / interval_seconds / default
      Removed value: -30
    • addedInput schema / properties / interval_seconds / description
      Added value: +"Default: 30."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it explains continuous background checks, the types of checks performed, alert generation, and plan-tier limits. It does not explain where alerts are delivered or what object/result is returned, leaving some operational behavior unspecified.

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?

The description is front-loaded with the core action and checks, then adds useful tier and alternative-tool context. It is somewhat long, but the plan-limit paragraph and see-also references earn their place.

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?

For a two-parameter tool with no output schema and no annotations, the description covers the key behavior, scope, tier limits, and alternatives well. It is slightly incomplete because it does not mention the return value or alert delivery mechanism.

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?

Schema coverage is 50%, so the description helps by clarifying `interval_seconds` as seconds between health checks and repeating the default of 30. `printer_name` is only described as 'Printer to monitor,' which is clear but minimal.

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?

States a specific verb and resource: 'Start continuous background health monitoring for a printer.' It also lists what the monitoring covers, making the tool's purpose distinct from ad-hoc checks.

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

Usage Guidelines5/5

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

Explicitly contrasts continuous watch monitoring with checking a printer yourself, naming `printer_status`, `monitor_print`, and `printer_snapshot` as alternatives. It also names `stop_printer_health_monitoring()` and `check_printer_health()` in the see-also list.

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