Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

archive_decoration_preset

Destructive

Archive a decoration preset to hide it from default listings while preserving all versions, branches, releases, and outcomes. Requires Kiln Pro.

Instructions

Archive a decoration preset — hide from default listings while preserving every version, branch, release, and outcome.

Needs Kiln Pro.

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": {
      "preset_id": "<preset_id>"
    },
    "name": "archive_decoration_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYesId of the preset to archive. Every version of it is flagged; ``versions_updated`` says how many.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / preset_id / description
      Added value: +"Id of the preset to archive.  Every version of it is flagged; ``versions_updated`` says how many."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered; the description adds real context by explaining that the operation is non-lossy — versions, branches, releases and outcomes are preserved — and that it requires a Kiln Pro tier. It does not flag reversibility explicitly (e.g., that unarchive_decoration_preset can undo it), but the preservation statement meaningfully informs the agent about blast radius.

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 with the core semantics front-loaded and the gating requirement isolated on its own line so it is easy to scan. Nothing is redundant or padded.

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 single-parameter mutation with annotations and no output schema, the description covers purpose, effect on existing data, and tier requirement — enough to call it correctly. The one gap is that reversibility/undo routing is left to the agent to discover from the sibling list.

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?

Only one parameter and schema description coverage is 100%, with the schema itself documenting preset_id and the versions_updated outcome. The description adds no syntax, format, or identifier-handling detail beyond the schema, so the baseline of 3 is appropriate.

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 (archive) and resource (decoration preset) and clarifies the semantics of archiving — hiding from default listings while retaining every version, branch, release and outcome — which distinguishes it from a delete. It never names the sibling it is the inverse of (unarchive_decoration_preset), so sibling differentiation is implicit rather than stated.

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?

"Hide from default listings while preserving..." implies the use case (retire something without data loss) and "Needs Kiln Pro" supplies a concrete prerequisite, which is genuinely useful gating information. However, there is no explicit when-not guidance and no pointer to unarchive_decoration_preset or delete/retire alternatives for an agent deciding between them.

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