Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

set_speed_schedule

Destructive

Configure layer-based print speed schedules with per-segment speed percentages and automatic adjustments, using a confirmation digest before any printer action runs.

Instructions

Set layer-based speed schedule with automatic adjustments (Pro).

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

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": {
      "schedule": "<schedule>"
    },
    "name": "set_speed_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleYesList of segments, each with ``from_layer`` (int), ``to_layer`` (int), ``speed_percent`` (int). Segments must not overlap. Gaps between segments are allowed (speed stays unchanged).
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_nameNoTarget printer name. Omit for default printer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / printer_name / description
      Added value: +"Target printer name.  Omit for default printer."
    • 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: \"\"."
    • addedInput schema / properties / schedule / description
      Added value: +"List of segments, each with ``from_layer`` (int), ``to_layer`` (int), ``speed_percent`` (int). Segments must not overlap. Gaps between segments are allowed (speed stays unchanged)."
  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 flag destructiveHint=true and readOnlyHint=false; the description adds meaningful context beyond that: the dry-run first phase runs nothing, the second phase executes exactly the enumerated actions through Kiln's own tools with their checks, and a Pro entitlement is required. It omits what happens to any pre-existing schedule and whether it is applied mid-print.

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?

Purpose is front-loaded in the first sentence and the mechanical explanation follows in one compact paragraph. The second paragraph is somewhat boilerplate-heavy but each clause carries real operational meaning.

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, fully-documented, non-read-only tool with no output schema, the definition covers the confirmation flow and entitlement. The remaining gap is the mutation's blast radius — whether an existing schedule is replaced — which matters given destructiveHint=true.

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 the schema already documents schedule, run_actions and printer_name in detail. The description reinforces the two-call run_actions semantics but adds nothing new about segment format or printer_name resolution, so the baseline 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?

States a specific verb and resource ('Set layer-based speed schedule') and adds a distinguishing modifier ('automatic adjustments', layer-based). It does not name which sibling it displaces (set_speed_percent, set_speed_profile, run_speed_schedule), so the agent must infer the boundary, but the layer-segmented nature is clear.

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 second paragraph gives a precise invocation protocol (first call returns actions and a digest, call again with that digest to execute), which is genuinely useful. It gives no guidance on when to pick this over set_speed_percent or set_speed_profile, and no stated preconditions beyond '(Pro)'.

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