Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

run_speed_schedule

Destructive

Run, report, or stop a layer-based print speed schedule, applying specified speed percentages as layers are reached and tracking what has been applied until completion or stop.

Instructions

Run, report or stop a layer-based speed schedule on this computer.

A schedule is a list of ``{"from_layer", "to_layer", "speed_percent"}``
segments.  With ``action="run"`` it starts on the printer that is
printing now, replacing a schedule already running for that printer:
the printer is asked which layer it is on every few seconds and each
segment's speed is set once, as the print reaches it.  It stops on its
own when the print ends, when the printer is found running a different
print, or on ``action="stop"`` (the printer stays at the last speed set).
``action="status"`` reports what has been applied so far.

Only the schedule's shape is checked here.  Which speeds suit this
printer and which layers a speed is unsafe on is decided by Kiln's
served ``set_speed_schedule``, which hands the checked schedule here.

Args:
    schedule: The segments to run (``action="run"`` only): a list of 1
        to 64 ``{"from_layer": int, "to_layer": int, "speed_percent":
        int}`` entries, ``speed_percent`` within 10-300.
    printer_name: Which printer.  Omit for the default printer.
    action: ``"run"`` (default), ``"status"`` or ``"stop"``.

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": "run_speed_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo``"run"`` (default), ``"status"`` or ``"stop"``. Default: "run".
scheduleNoThe segments to run (``action="run"`` only): a list of 1 to 64 ``{"from_layer": int, "to_layer": int, "speed_percent": int}`` entries, ``speed_percent`` within 10-300.
printer_nameNoWhich printer. Omit for the default printer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / action / description
      Previous value: -"Default: \"run\"."New value: +"``\"run\"`` (default), ``\"status\"`` or ``\"stop\"``. Default: \"run\"."
    • addedInput schema / properties / printer_name / description
      Added value: +"Which printer.  Omit for the default printer."
    • addedInput schema / properties / schedule / description
      Added value: +"The segments to run (``action=\"run\"`` only): a list of 1 to 64 ``{\"from_layer\": int, \"to_layer\": int, \"speed_percent\": int}`` entries, ``speed_percent`` within 10-300."
  2. Addedv1.5.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses meaningful behavior: it replaces a running schedule, polls the printer's layer every few seconds, applies each segment once, and self-terminates on print end, print change, or stop, leaving the printer at the last speed. It does not mention permissions or failure modes if the printer is idle, which keeps it from a 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 prose is front-loaded and well organized, with the lifecycle behavior stated before the Args block. The Args section duplicates the schema descriptions almost verbatim, which is some wasted space.

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 three-parameter mutation tool with no output schema, the description covers lifecycle, termination conditions, action semantics, and validation boundaries. An agent has everything needed to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the 'action="run" only' constraint on schedule and clarifies that omitting printer_name targets the default printer. The Args block largely restates the schema, limiting the added value.

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+resource ('Run, report or stop a layer-based speed schedule on this computer') and immediately defines what a schedule is. It is clearly distinguishable from siblings like set_speed_percent and set_speed_schedule, the latter of which is explicitly named as the validation layer.

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?

It spells out the three actions and their conditions, states that run replaces an existing schedule for the currently printing printer, and routes speed-suitability decisions to Kiln's served set_speed_schedule. The division of responsibility between this tool and its sibling is explicit.

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