Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rename_printer

Destructive

Rename a saved 3D printer and carry its print history, loaded material, queued jobs, e-stop state and standing permissions to the new name. Refuses when busy or the name is taken, leaving the printer unchanged.

Instructions

Give a saved printer a new name; its records come with it.

        The printer's print history and outcomes, what is loaded in it,
        its queued jobs, its emergency-stop state and the standing
        permissions on this computer that name it all move to the new
        name, so the machine's record stays one record.  The reply
        says what came along (``carried``), which standing permissions
        followed and which were turned off (``permissions``), and the
        names the printer has had (``formerly``).  The machine itself,
        its address and its credentials are untouched.

        Refused, with nothing changed, when the printer is printing or
        Kiln is following a print on it (``PRINTER_BUSY``), when the new
        name is already another printer's (``NAME_TAKEN``), or when the
        new name carries the printer's address, serial or a code
        (``NAME_HAS_IDENTIFIER``: the reply's ``suggested_name`` is a
        clean one to offer instead).  Runs on the computer the printer
        is set up on, never on Kiln's servers.

        Args:
            printer_name: The printer's current name.
            new_name: What to call it from now on.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "printer_name": "<printer_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_printer"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesWhat to call it from now on.
printer_nameYesThe printer's current name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses exactly what moves with the rename, what remains untouched, which permissions follow or are disabled, and the response fields carried, permissions, and formerly. It also documents refusal conditions, error codes, suggested_name behavior, and that execution happens on the local computer rather than Kiln servers.

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 the core action and consequence, and the following paragraphs are organized around behavior, refusals, and execution location. It is somewhat verbose and repeats the argument meanings, but most sentences carry useful operational detail.

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 two-parameter mutation tool with no output schema, the description is complete enough to call correctly: it explains side effects, what is preserved, return fields, refusal modes, and execution environment. An agent has the information needed to anticipate outcomes and handle errors.

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%, so both parameters are already documented in the schema. The description repeats that printer_name is the current name and new_name is what to call it from now on, without adding format constraints beyond the refusal rules already described elsewhere.

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 opens with a specific verb and resource: 'Give a saved printer a new name.' It immediately distinguishes this from generic renaming by explaining that associated records move with it, so an agent can identify the operation precisely.

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?

It clearly defines when the rename will be refused, including PRINTER_BUSY, NAME_TAKEN, and NAME_HAS_IDENTIFIER, and says nothing changes on refusal. It does not explicitly compare this against an alternative sibling tool, but the usage context is strong.

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