Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

kiln_monitor_control

Relays pause, resume, or cancel commands from Kiln's inline print monitor panel to a 3D printer, routing them through the same controls used by the pause, resume, and cancel print actions.

Instructions

Internal support for Kiln's inline print monitor.

        Relays a pause, resume, or cancel from the panel's own buttons
        through the same doors the pause_print, resume_print and
        cancel_print tools open.  Called by the panel itself; not
        useful to call directly.

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": {
      "action": "<action>"
    },
    "name": "kiln_monitor_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
printer_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool relays pause/resume/cancel actions, but does not describe side effects, permissions, reversibility, or whether cancel is destructive, leaving meaningful gaps for a mutation-like control 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 short and front-loaded, first identifying the tool's role and then immediately stating the critical usage limitation. Every sentence adds useful information with no redundancy.

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?

For an internal-only tool meant to be invoked by the panel, the description sufficiently communicates that agents should not call it directly. However, with no output schema and 0% parameter description coverage, it leaves the two input parameters undocumented for any caller that does need to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it does not mention the 'action' or 'printer_name' parameters at all. It implicitly names pause, resume, and cancel as valid actions, but does not map these to the action parameter or explain the nullable printer_name.

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?

States a specific verb and resource: it relays pause, resume, or cancel commands from the Kiln inline print monitor panel. It also explicitly distinguishes itself from the pause_print, resume_print, and cancel_print sibling tools by saying it uses the 'same doors' those tools open.

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 it is called by the panel itself and is 'not useful to call directly,' which is clear when-not-to-use guidance. It also names the sibling tools whose functionality it mirrors, giving the agent obvious alternatives.

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