Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rollback_decoration

Destructive

Restore an earlier saved decoration version without rewriting history; the current version is archived and the restored one returns as a new version.

Instructions

Restore an earlier version of a saved decoration (Kiln Pro).

        The current version is archived and the earlier one comes back
        as a NEW version number, so history is never rewritten.

        :param name: Decoration name or slug.
        :param version: Version number to restore.
        :returns: Dict with the restored decoration.

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": {
      "name": "<name>",
      "version": "<version>"
    },
    "name": "rollback_decoration"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDecoration name or slug.
versionYesVersion number to restore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / name / description
      Added value: +"Decoration name or slug."
    • addedInput schema / properties / version / description
      Added value: +"Version number to restore."
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the key behavioral nuance: the current version is archived and the restored one becomes a NEW version number, so history is never rewritten. That materially reframes what 'destructive' means here and adds a tier requirement ('Kiln Pro') that annotations cannot express. It stops short of stating permission requirements or whether the archival step can be undone.

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 behavioral explanation is front-loaded in the second sentence, and the whole definition is only a few lines. Minor waste comes from the Sphinx ':param'/':returns' boilerplate, which duplicates the schema fields instead of adding information.

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 two-parameter mutation with no output schema, the definition covers purpose, the state change and its history guarantees, the plan gate, and the return type. There is no output schema, so the ':returns: Dict with the restored decoration' line is a useful minimum rather than a gap.

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 the schema already documents both parameters. The docstring's ':param name/version' lines restate the same wording verbatim rather than adding meaning, such as accepted slug formats or how to discover valid version numbers. Baseline 3 is the right level when the schema carries the semantics.

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 states a precise verb and object ('Restore an earlier version of a saved decoration') and scopes it to decorations, which separates it from the many other rollback/restore siblings (rollback_design_version, rollback_feature, restore_from_reflog_entry). The parenthetical '(Kiln Pro)' further identifies the product surface it belongs to.

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 implied rather than stated: an agent can infer 'use this to revert a decoration to an older version,' but the description never says when to prefer this over alternatives such as decoration_history, list_decorations, or re-applying a saved decoration. No exclusions or prerequisites for choosing this tool 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