Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_resume

Destructive

Resume paused 3D prints across selected printers using a confirm-first action plan: the first call returns actions and a digest, then rerun with that digest to execute.

Instructions

Resume paused prints across the whole fleet (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_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoSend the resume even where Kiln believes the printer is not paused (same escape hatch as ``resume_print``). Default: false.
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 resume. Omit for every registered machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / force / description
      Previous value: -"Default: false."New value: +"Send the resume even where Kiln believes the printer is not paused (same escape hatch as ``resume_print``). Default: false."
    • addedInput schema / properties / printer_names / description
      Added value: +"Which printers to resume.  Omit for every registered machine."
    • 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, and the description reinforces this by disclosing the two-phase dry-run protocol: the first call answers with intended actions and an actions_digest but 'runs nothing', and the second executes them through Kiln's other tools with their checks. It also notes the tool may act on the local printer, which is useful cross-context behavior. It does not cover failure behavior across a mixed fleet, keeping it below 5.

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 sentence and the protocol explanation follows logically. The parenthetical list of actions ('upload, start, pause, resume, set a speed preset') is somewhat broader than this tool's actual job and adds mild noise.

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 destructive, fleet-wide mutation with no output schema, the description covers the tier gate, the confirmation protocol, the digest handshake, and the fact that actions run through Kiln's existing checked tools. Only edge behavior such as partial failures or per-printer error reporting is left unaddressed.

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 100%, so all three parameters (force, run_actions, printer_names) are already documented in the schema. The description only restates the run_actions handshake, adding no new format or semantics beyond the schema, so the baseline of 3 applies.

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 names a specific verb and scope: "Resume paused prints across the whole fleet," and flags the Business tier. That clearly separates it from the single-printer resume_print, but the description never names that sibling explicitly, so the distinction is inferred from the word "fleet" rather than stated.

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?

It gives strong procedural guidance for the two-phase call (first call returns a plan, second call with run_actions executes it). However, it never states when to choose this over resume_print or fleet_pause, or when not to use it, so selection guidance is only implied by the fleet scope.

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