Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

retire_decoration_preset_release

Destructive

Retire a decoration preset release to keep its record preserved while stopping the name from resolving; add an optional reason for the retirement.

Instructions

Yank a preset release — record preserved, name stops resolving.

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": {
      "release_id": "<release_id>"
    },
    "name": "retire_decoration_preset_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoFree-text reason (an advisory, a bad revision). Default: "".
release_idYesThe release to retire, as ``list_decoration_preset_releases`` returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / reason / description
      Previous value: -"Default: \"\"."New value: +"Free-text reason (an advisory, a bad revision). Default: \"\"."
    • addedInput schema / properties / release_id / description
      Added value: +"The release to retire, as ``list_decoration_preset_releases`` returns it."
  2. Addedv1.5.0

TDQS

A3.6/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 covered. The description still earns credit by adding non-obvious semantics: the release record is not deleted, only name resolution stops, plus a tier gate. It does not say whether retirement can be undone, which is the remaining behavioral gap.

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?

Two short sentences, front-loaded with the action and effect, then the prerequisite. No wasted words; the only slight cost is the colloquial "Yank," which is informal but unambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with full schema coverage and no output schema, the description covers effect and prerequisites. It is still silent on reversibility/undo paths and on what happens to dependents of the retired name — meaningful omissions for a destructive operation.

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%, including a description for release_id that points at list_decoration_preset_releases and a note that reason is advisory free text. The description adds nothing beyond the schema, so the 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?

"Yank a preset release" pairs a specific verb with the exact resource, and the second clause pins down the effect (record preserved, name stops resolving). It clearly is not the branch- or design-release variants, though the description never explicitly contrasts them, relying on the tool name for that distinction.

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?

"Needs Kiln Pro" supplies a real prerequisite that tells the agent when the call will succeed. However, there is no guidance on when to retire a release versus using a sibling (e.g., retire_decoration_preset_branch, cloud_push_preset_release, verify_decoration_preset_release), and no statement about irreversibility or when-not to call it.

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