Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

printer_status

Read-only

Retrieves current printer state, temperatures, job progress, and capabilities. Use it as the first call to understand what the printer is doing.

Instructions

Get printer state, temperatures, job progress, and capabilities.

Returns a JSON object with:
- ``printer``: connection status, operational state, tool/bed temperatures
- ``job``: current file name, completion percentage, elapsed and remaining time
- ``capabilities``: what this printer backend supports (``full`` only)

Use this as the first call to understand what the printer is doing.

Args:
    printer_name: Target printer.  Omit for the default printer.
    detail: ``"full"`` (default) for everything, or ``"lite"`` for
        frequent polling during a print — same field names, but
        ``capabilities`` is omitted and ``printer`` is trimmed to the
        readings that actually move.  Both levels carry every warning.

``detail`` exists so polling and inspection share ONE vocabulary.  The
retired ``print_status_lite`` returned the same numbers under different
names (``completion_pct``, ``hotend_temp``), which is why clients grew
defensive key-alias lists to read either shape.

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

Input Schema

NameRequiredDescriptionDefault
detailNo``"full"`` (default) for everything, or ``"lite"`` for frequent polling during a print — same field names, but ``capabilities`` is omitted and ``printer`` is trimmed to the readings that actually move. Both levels carry every warning. Default: "full".
printer_nameNoTarget printer. Omit for the default printer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / detail / description
      Previous value: -"Default: \"full\"."New value: +"``\"full\"`` (default) for everything, or ``\"lite\"`` for frequent polling during a print — same field names, but ``capabilities`` is omitted and ``printer`` is trimmed to the readings that actually move.  Both levels carry every warning. Default: \"full\"."
    • addedInput schema / properties / printer_name / description
      Added value: +"Target printer.  Omit for the default printer."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / detail / default
      Removed value: -"full"
    • addedInput schema / properties / detail / description
      Added value: +"Default: \"full\"."
    • removedInput schema / properties / printer_name / default
      Removed value: -null
  3. Changed2 schema fields changedv1.3.1
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "full",
+  "title": "Detail",
+  "type": "string"
+}
    • addedInput schema / properties / printer_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Printer Name"
+}
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, and non-destructive behavior. The description adds meaningful return-shape details and explains the lite-mode trimming behavior and warning coverage, though it does not discuss errors or rate limits.

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 first sentence front-loads what the tool does, followed by a clear return-value breakdown and usage notes. It is somewhat verbose and includes a historical digression about a retired tool, but the structure is easy to scan.

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?

Because there is no output schema, the description appropriately explains the returned JSON structure and detail-level differences. It is complete for calling the tool, but in a large sibling set it should better distinguish itself from other printer-monitoring tools.

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 description essentially repeats the parameter documentation already present in the schema. The rationale about one vocabulary across polling and inspection adds some value, but no syntax or constraints beyond the schema.

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?

The description gives a specific verb and resource: get printer state, temperatures, job progress, and capabilities. It clearly distinguishes itself from the retired print_status_lite tool, but does not distinguish itself from active siblings such as printer_snapshot, monitor_print, or watch_print_status.

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

Usage Guidelines4/5

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

The description explicitly says to use this as the first call to understand printer activity, and explains when to choose detail='lite' for frequent polling during a print. It does not name alternative current tools or say when not to use this one.

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