Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_decoration

Destructive

Delete a decoration preset to retire it (recoverable) or erase it permanently.

Instructions

Delete a decoration preset — retire it (default, recoverable) or erase it permanently.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoEcho ``preset_id`` here to execute. Omit on the first call to see the confirmation prompt. Default: "".
permanentNo``False`` (default) retires; ``True`` erases. Default: false.
preset_idYesThe decoration preset to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Default: \"\"."New value: +"Echo ``preset_id`` here to execute. Omit on the first call to see the confirmation prompt. Default: \"\"."
    • changedInput schema / properties / permanent / description
      Previous value: -"Default: false."New value: +"``False`` (default) retires; ``True`` erases. Default: false."
    • addedInput schema / properties / preset_id / description
      Added value: +"The decoration preset to delete."
  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, but the description adds genuinely new behavioral context: the default path is a recoverable retire while the opt-in flag causes permanent erasure. That is exactly the risk distinction an agent needs. It omits the two-step confirm/echo handshake, though the schema covers that.

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?

One tight sentence, front-loaded with the verb and resource, with the mode distinction delivered in a compact parenthetical. Zero filler or repeated 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?

For a simple three-parameter deletion tool with full schema coverage and no output schema, the description supplies the key safety posture (default recoverable vs permanent erase). The only real gap is the absence of any note about the confirmation step or expected failure modes, which the schema largely absorbs.

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% — preset_id, permanent, and the confirm echo are all documented in the schema itself, including the 'omit on first call to see the confirmation prompt' behavior. The description's 'retire it (default) or erase it permanently' merely mirrors the permanent parameter, adding no syntax or edge-case detail beyond it.

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 ('Delete a decoration preset') and immediately disambiguates the two deletion modes (retire vs permanent erase). It does not, however, distinguish itself from adjacent siblings such as archive_decoration_preset, unarchive_decoration_preset, or the retire_* preset-branch tools, so an agent could still hesitate between them.

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?

The parenthetical implies when each mode applies (default = recoverable, permanent = irreversible), which is usable guidance. But there is no explicit 'use this when…' statement, no mention of the required confirmation workflow, and no pointer to archive_decoration_preset as the alternative for non-destructive hiding.

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