Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

print_status_lite

Retrieve current printer status with job progress and nozzle temperature in a nested structure. Deprecated; call printer_status with detail='lite' instead.

Instructions

DEPRECATED — call printer_status(detail="lite") instead.

Kept so an existing caller does not break.  It now delegates, and
therefore returns ``printer_status``'s shape: nested ``printer`` /
``job`` blocks, not the flat ``completion_pct`` / ``hotend_temp``
keys this tool used to invent.  That rename was the whole problem —
two tools describing one nozzle temperature with two different words,
which is why clients grew alias lists to read either.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses that the tool delegates to printer_status, explains the return shape change (nested printer/job vs flat keys), and details the historical naming problem. No behavioral traits are hidden.

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 somewhat verbose but well-structured: deprecation, delegation, shape change, reason, then args. It could be slightly more concise but the extra detail is necessary for context.

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?

It comprehensively covers the deprecation, replacement, return shape, historical problem, and parameter usage. For a deprecated wrapper, it leaves no relevant context unexplained.

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?

The Args section adds meaning to printer_name: 'Target printer. Omit for the default printer.' This exceeds the schema info (optional, default null) and clarifies usage.

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 identifies the tool as a deprecated alias for printer_status with detail='lite', and states its role as a backward-compatibility wrapper. This distinguishes it from sibling tools like printer_status.

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 instructs to call printer_status(detail='lite') instead, making the alternative clear. The deprecation notice provides direct guidance on when not to use this tool.

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

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