Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fleet_set_speed

Destructive

Set a target speed percentage for all registered 3D printers in a Kiln fleet; first call returns planned actions and a digest, then rerun with that digest to execute them.

Instructions

Set speed across all registered printers in the 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

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

Input Schema

NameRequiredDescriptionDefault
percentYesTarget speed as a percentage of the sliced speed (100 = as sliced), applied to every registered printer. A value outside a printer's own range is refused for that printer, and a printer with fixed speed presets takes the nearest one; the reply says which.
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: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / percent / description
      Added value: +"Target speed as a percentage of the sliced speed (100 = as sliced), applied to every registered printer.  A value outside a printer's own range is refused for that printer, and a printer with fixed speed presets takes the nearest one; the reply says which."
    • 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

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the dry-run/confirm choreography, that nothing is executed on the first call, and that execution is delegated to Kiln's own tools with all of their checks. This complements destructiveHint=true with concrete mechanics an agent needs before invoking a fleet-wide mutation.

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?

Two short paragraphs, scope stated first, then the protocol. The second sentence is long and stacks several clauses (ask, answer, confirm, delegate), but every clause carries load; '(Business)' is the only unexplained fragment.

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?

With no output schema, the description correctly explains what comes back (proposed actions plus a digest and rationale) and how to confirm. For a destructive fleet-wide mutation it could add failure/partial-application behavior across printers, but the critical call protocol and safety posture are complete.

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%, and the schema already documents percent semantics (percentage of sliced speed, out-of-range refusal, nearest preset) and run_actions. The description's parameter value is limited to tying run_actions to the returned actions_digest, which the schema also states, so this sits at the baseline.

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?

States a specific verb and resource with explicit scope: set speed across 'all registered printers in the fleet'. That scope phrase is what separates it from single-printer siblings like set_speed_percent or set_speed_profile without needing to open their schemas.

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

Usage Guidelines4/5

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

Gives clear operating guidance for the two-call protocol: first call returns proposed actions and an actions_digest and runs nothing; call again with that digest to execute. It does not, however, name when to prefer this over single-printer speed tools or what tier/Business gating means in practice, so alternatives remain for the agent to infer.

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