Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

revert_calibration_recommendations

Destructive

Restore default calibration settings by undoing all calibration changes Kiln applied, returning the printer profile to its original state.

Instructions

Undo every calibration change Kiln applied and go back to the defaults.

Needs Kiln Pro.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, so the safety profile is known. The description adds two things annotations cannot: the blast radius (every change, with no selective revert) and the terminal state (defaults restored), plus a Kiln Pro entitlement gate that affects whether the call can succeed at all. It stops short of saying whether the revert is itself undoable.

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

Conciseness5/5

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

Two short sentences, zero filler, with the action and its end state front-loaded and the prerequisite demoted to a trailing line. Nothing could be removed without losing information.

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 parameters, no output schema, and destructive semantics already flagged by annotations, the description covers what an agent needs to decide and call. The remaining gap is whether prior settings can be recovered after the revert, which matters for a destructive operation but is a minor omission here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly signals the all-or-nothing, no-argument nature of the operation.

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?

"Undo every calibration change Kiln applied" states a specific verb (undo/revert) and a precisely scoped resource, and "go back to the defaults" names the resulting state. An agent can distinguish this from the sibling apply_calibration_recommendations by the direction of the operation, though the sibling is never named explicitly.

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?

Usage is only implied: the agent must infer that this is the escape hatch when applied recommendations need to be backed out. The one explicit guideline is the entitlement constraint "Needs Kiln Pro," which is useful but limited. No when-not conditions or named alternatives are given.

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