Skip to main content
Glama

print_status_lite

Poll print status with minimal fields for efficient monitoring. Returns state, completion %, file name, ETA, and temps for frequent updates during prints.

Instructions

Lightweight print status — minimal fields for efficient agent polling.

Returns only state, completion %, file name, ETA, and temps.
Use this for frequent polling during prints. For full detail
(capabilities, all flags, full job data), use ``printer_status``.
For a formatted text report with cost estimate and health commentary,
use ``monitor_print``.

Args:
    printer_name: Target printer.  Omit for the default printer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameNo
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It lists the returned fields but does not explicitly state that the tool is read-only or has no side effects, which is expected for a polling tool.

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 extremely concise with no wasted words: two sentences for purpose and usage plus one line for the parameter. It is front-loaded and easy to parse.

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?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description adequately covers what it does and returns. It lists the returned fields, which is sufficient for an agent to understand the output, though format details are omitted.

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?

The description explains the single parameter (printer_name) as the target printer and notes it can be omitted for default, adding meaning beyond the schema's type definition. Schema description coverage is 0%, so the description compensates well.

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 provides lightweight print status with specific fields (state, completion %, file name, ETA, temps) and distinguishes from siblings by naming alternatives for full detail and formatted reports.

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 says to use this tool for frequent polling during prints, and provides specific alternatives (printer_status for full detail, monitor_print for formatted report) when more information is needed.

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