Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

release_printer_lock

Destructive

Release a printer reservation held by the current session, or force-release another session's reservation to make the printer available.

Instructions

End this session's reservation of a printer, or, with force, any session's.

        Args:
            printer_name: Printer to release.
            holder: Unused: a reservation belongs to the Kiln session that
                made it.  Accepted so earlier calls keep working.
            force: Also end a reservation another Kiln session made.

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>"
    },
    "name": "release_printer_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoAlso end a reservation another Kiln session made. Default: false.
holderNoUnused: a reservation belongs to the Kiln session that made it. Accepted so earlier calls keep working. Default: "".
printer_nameYesPrinter to release.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Also end a reservation another Kiln session made. Default: false.",
+  "title": "Force",
+  "type": "boolean"
+}
    • changedInput schema / properties / holder / description
      Previous value: -"Default: \"agent\"."New value: +"Unused: a reservation belongs to the Kiln session that made it.  Accepted so earlier calls keep working. Default: \"\"."
    • addedInput schema / properties / printer_name / description
      Added value: +"Printer to release."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / holder / default
      Removed value: -"agent"
    • addedInput schema / properties / holder / description
      Added value: +"Default: \"agent\"."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the crucial detail of what is actually destroyed: a reservation, which belongs to the Kiln session, and 'force' can terminate a reservation belonging to a *different* session. It also discloses the backward-compatibility oddity of the unused 'holder' parameter, which an agent could otherwise misinterpret. It does not say what happens if no reservation is held or whether the call is idempotent.

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 operative sentence is front-loaded and precise. The Args block largely duplicates the input schema and could be dropped without loss, but it is short and does not obscure the main statement.

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

Completeness3/5

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

There is no output schema, so the description should say what the tool returns or how it signals that no reservation existed; it is silent on return values, error cases, and idempotency. For a destructive three-parameter mutation tool it covers the intent well but leaves the outcome unspecified.

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% and the Args block restates the schema descriptions almost verbatim, so the description adds no new parameter meaning. The 'holder is unused/legacy' note is the only interpretation help, and it is already present in the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb ('End') and resource ('reservation of a printer') and distinguishes the default scope (this session) from the forced scope (any session). It does not name the complementary siblings such as acquire_printer_lock or hand_back_printer, so the reader must infer the pairing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The condition for using 'force' is stated explicitly ('any session's'), which is genuine when-to guidance for the risky path. However, there is no guidance on when to call release at all versus handing off the printer (hand_back_printer) or simply letting the session end, and no prerequisite or ordering advice.

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