Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_pause

Destructive

Pause printing across your whole 3D printer fleet, or only named machines, while holding bed temperatures. The first call returns a digest of planned actions; call again with it to run them.

Instructions

Pause printing across the whole fleet, gracefully (Business).

This tool may ask this computer to act on your printer (upload, start, pause, resume, set a speed preset). It first answers with the actions it wants and why, and runs nothing; call it again with run_actions set to the actions_digest it answered with to carry out exactly those actions through Kiln's own tools here, with every check those tools make.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fleet_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
keep_tempsNoTrue (the default) holds each bed at temperature and settles each nozzle during the pause; False leaves both heaters to the printer's own pause behaviour. Default: true.
run_actionsNoLeave empty on the first call: the tool answers with the actions it wants and an actions_digest, and runs nothing. Call again with that digest here to carry out exactly those actions. Default: "".
printer_namesNoWhich printers to pause. Omit for every registered machine (each physical machine once, even when it is registered under two names).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / keep_temps / description
      Previous value: -"Default: true."New value: +"True (the default) holds each bed at temperature and settles each nozzle during the pause; False leaves both heaters to the printer's own pause behaviour. Default: true."
    • addedInput schema / properties / printer_names / description
      Added value: +"Which printers to pause.  Omit for every registered machine (each physical machine once, even when it is registered under two names)."
    • changedInput schema / properties / run_actions / description
      Previous value: -"Default: \"\"."New value: +"Leave empty on the first call: the tool answers with the actions it wants and an actions_digest, and runs nothing. Call again with that digest here to carry out exactly those actions. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real value by disclosing the dry-run-then-confirm pattern and that execution is routed through Kiln's own tools with their checks intact. It still doesn't say what 'gracefully' means operationally (nozzle settle, heater behaviour) or that the pause is reversible via fleet_resume.

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 purpose is front-loaded in the first clause and the two-step confirmation follows logically. The second sentence is a long run-on with a filler tail ('with every check those tools make') that could be trimmed, but no sentence is wasted entirely.

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?

For a three-parameter, no-output-schema mutation tool with full schema coverage and annotations, the description supplies the missing piece an agent needs: the mandatory confirm round-trip. It omits fleet-wide partial-failure behaviour and the recovery path, which would matter for a destructive fleet operation.

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 the schema already documents keep_temps, run_actions, and printer_names thoroughly. The description reinforces the run_actions digest contract but adds no new semantics for keep_temps or for the deduplication behaviour of printer_names. Baseline 3 is appropriate.

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 description opens with a specific verb and resource plus scope: 'Pause printing across the whole fleet, gracefully.' That distinguishes it from the single-machine pause_print and from fleet_resume/fleet_cancel without naming them explicitly. The parenthetical '(Business)' is tier metadata, not purpose, and no sibling is named, so it stops short of a 5.

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?

Usage is implied by the two-step protocol (first call returns actions and a digest, second call with run_actions executes them), which tells the agent how to invoke it but not when to choose it over pause_print, fleet_cancel, or pipeline_pause. No exclusions or prerequisites (e.g. tier requirement, printer online state) are stated.

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