Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

retire_feature_release

Destructive

Yank a feature release so its record remains preserved but the name no longer resolves; use it to withdraw an advisory or bad revision.

Instructions

Yank a feature 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_feature_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoFree-text reason (an advisory, a bad revision). Default: "".
release_idYesThe release to retire, as ``list_feature_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_feature_releases`` returns it."
  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 flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: it discloses that the underlying record is preserved and only the name stops resolving (a soft retire rather than a hard delete), plus the Kiln Pro entitlement requirement, which is a genuine auth/tier constraint.

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 lines, zero filler, with the effect statement front-loaded and the entitlement requirement isolated on its own line where it is easy to scan.

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 two-parameter destructive tool with full schema coverage and no output schema, the description covers what happens, what survives, and what tier is required. The remaining gap is recoverability — whether a retired release can be restored — which matters for a destructiveHint=true 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 description coverage is 100% — release_id's schema text already says it comes from list_feature_releases and reason is documented as free text. The description adds nothing about either parameter, 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 feature release" names a specific verb and resource, and the follow-on clause explains the exact effect (record kept, name no longer resolves). It is clear against delete_feature or archive_feature, but it never explicitly distinguishes itself from the near-identical sibling retire_feature_branch, which an agent could easily confuse with it.

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 "Needs Kiln Pro" line is a useful precondition, but there is no when-to-use versus when-to-use-something-else guidance — nothing tells the agent to prefer archive_feature or retire_feature_branch instead, and no statement about whether the retirement can be undone.

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