Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

rollback_printer_firmware

Roll back firmware on a specific printer by name in multi-printer setups, with optional version pinning to a target version.

Instructions

Rollback firmware on a specific printer by name (fleet-level, supports version pinning).

        Use this in multi-printer setups. For single-printer setups, use ``rollback_firmware`` instead.

        Args:
            printer_name: Printer to rollback.
            target_version: Specific version to rollback to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameYes
target_versionNo

Tool Definition Quality

A4/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It fails to disclose destructive nature, required permissions, side effects, or error conditions of a firmware rollback operation.

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 concise, front-loaded with the main purpose, and includes a structured Args section with no wasted sentences.

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 complexity (firmware rollback, multi-printer context) and no output schema, the description is reasonably complete but could detail post-rollback behavior or safety aspects.

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 coverage is 0%, so description must compensate. It lists parameters with brief descriptions ('Printer to rollback', 'Specific version to rollback to'), adding basic meaning but lacking format or constraints.

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 the tool rolls back firmware on a specific printer by name, with fleet-level and version pinning support. It distinguishes from the sibling 'rollback_firmware' tool for single-printer setups.

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 advises to use this tool in multi-printer setups and directs to an alternative (rollback_firmware) for single-printer setups, providing clear usage context.

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