Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

set_speed_percent

Destructive

Set a 3D printer's speed to a custom percentage so you can adjust print pace for the current job.

Instructions

Set printer speed to a custom percentage (Pro feature).

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": {
      "percent": "<percent>"
    },
    "name": "set_speed_percent"
  }
}

Input Schema

NameRequiredDescriptionDefault
percentYesSpeed percentage (e.g. 115 for 115%).
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 / percent / description
      Added value: +"Speed percentage (e.g. 115 for 115%)."
    • 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: \"\"."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is structured. The description still adds real value beyond them: the Pro-tier gate and, crucially, the two-phase confirm protocol where the first call runs nothing and returns an actions_digest that must be echoed back before anything executes. It stops short of saying what 'destructive' concretely means here (e.g. mid-print consequences).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and tight, but the second paragraph is cross-cutting boilerplate enumerating unrelated actions ('upload, start, pause, resume') that do not apply to this tool, which dilutes focus. The confirmation requirement is worth stating, though it could be shortened considerably.

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?

With three fully documented parameters, no output schema, and annotations covering safety, the definition is callable as written. Gaps remain: no percent bounds or relative-vs-absolute semantics, no note on whether the change affects an in-progress print or persists, and no differentiation from the other speed-setting tools.

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 percent, run_actions, and printer_name are already documented in the schema. The description's protocol paragraph largely restates the run_actions semantics rather than adding new meaning such as valid percent ranges or behavior relative to an active speed profile, so 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?

The first sentence gives a specific verb and resource with the value shape called out ('Set printer speed to a custom percentage') and adds a tier qualifier ('Pro feature'). It does not distinguish this from close siblings such as set_speed_profile, set_speed_schedule, run_speed_schedule, or fleet_set_speed, so an agent still has to infer which speed tool applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this over set_speed_profile or set_speed_schedule, and no prerequisites beyond the 'Pro feature' note. The second paragraph explains the invocation protocol rather than when-to-use, so selection guidance is effectively absent.

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