Skip to main content
Glama

monitor_print

Create a one-shot print status report: progress, temperatures, speed, cost, ETA, and snapshot. Quickly verify printer health and remaining time.

Instructions

One-shot print status report (human-readable text: progress, temps, speed, cost, ETA).

Use for quick status checks. Returns a fixed-format text report with
progress, temps, speed, errors, cost estimate, camera snapshot, and
health commentary. For structured data + AI vision inspection, use
``monitor_print_vision``. For persistent background monitoring, use
``watch_print``.

:param printer_name: Target printer name.  Omit for the default printer.
:param include_snapshot: Whether to capture and save a camera snapshot.
:param brief_id: Optional saved-goal id from ``design_session``.  When
    the brief resolves, the report appends a single ``Goal:`` line
    with the design's duty and environment — so the agent watching
    a print can answer "is this the right design for the goal?"
    without a separate lookup.  Best-effort: a missing kiln-pro
    install or an unresolvable brief silently skips the line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brief_idNo
printer_nameNo
include_snapshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that it is one-shot, returns a fixed-format text, includes snapshot behavior, and notes best-effort behavior for brief_id (silent skip on failure). It does not explicitly state read-only nature, but 'status report' strongly implies no side effects.

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?

The description is well-structured with a clear purpose sentence, usage guidance, and parameter documentation. Every sentence adds value with no redundancy or fluff.

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

Completeness5/5

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

For a tool with 3 optional parameters and an output schema, the description covers purpose, usage, return format (progress, temps, speed, errors, cost estimate, camera snapshot, health commentary), parameter behaviors, and distinguishes two sibling tools. The presence of an output schema means return structure is covered elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters (printer_name, include_snapshot, brief_id) are explained with meaningful context beyond the schema's bare titles. The :param lines clarify defaults and behavior (e.g., 'Omit for default', 'Best-effort: a missing kiln-pro install... silently skips the line'). Schema coverage is 0%, so description fully compensates.

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?

The description clearly states it is a 'one-shot print status report' returning human-readable text with specific fields. It distinguishes itself from two sibling tools: monitor_print_vision (structured data + AI vision) and watch_print (persistent monitoring).

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 states 'Use for quick status checks' and provides when-not-to-use guidance with alternatives: 'For structured data + AI vision inspection, use monitor_print_vision. For persistent background monitoring, use watch_print.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server