Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unarchive_decoration_preset

Destructive

Restore a previously archived decoration preset to default listings in Kiln, unflagging all its versions; requires Kiln Pro.

Instructions

Restore a previously-archived decoration preset to default listings.

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

Input Schema

NameRequiredDescriptionDefault
preset_idYesId of the archived preset to restore. Every version of it is unflagged.

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 archived preset to restore.  Every version of it is unflagged."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=false, so the safety profile is covered. The description adds the meaningful business outcome ('default listings') and the tier gate. It doesn't say what state the preset must be in or what happens to listings that referenced it while archived.

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 sentences, zero filler, effect stated before the prerequisite. Nothing to trim and nothing buried.

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 state-flip with no output schema, the description covers purpose, effect, and tier requirement. Minor gaps remain around preconditions (must the preset actually be archived?) and the response, but nothing an agent likely gets wrong.

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 preset_id description already explains that every version of the preset is unflagged. The tool description adds nothing about the parameter, 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?

States a specific verb and resource (restore an archived decoration preset) plus the observable effect (back into default listings). The 'unarchive' prefix makes the inverse relationship with archive_decoration_preset obvious, though it never names that sibling 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?

Adds one real precondition, 'Needs Kiln Pro', which tells the agent when the call is viable. It gives no guidance on when-not to call, what to do if the preset is already active, or how it relates to the archive/retire siblings.

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