Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_decoration_preset_releases

Read-only

List signed decoration-preset releases and retrieve the release ID needed to apply a preset; optionally filter by preset or include retired releases. Requires Kiln Pro.

Instructions

List signed decoration-preset releases — and the id needed to apply one.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_decoration_preset_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idNoRestrict to one preset (default: all).
include_retiredNoWhen true, retired releases are listed too. Off by default. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / include_retired / description
      Previous value: -"Default: false."New value: +"When true, retired releases are listed too.  Off by default. Default: false."
    • addedInput schema / properties / preset_id / description
      Added value: +"Restrict to one preset (default: all)."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/non-destructive annotations it discloses three useful traits: only signed releases are returned, the response contains the id required for applying a preset, and the tool is gated behind Kiln Pro. Pagination or result-size behavior is unstated, which keeps it below a 5.

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 action and purpose front-loaded, followed by the single prerequisite. 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 simple two-parameter read tool with no output schema, the description covers purpose, the key returned value, and the tier requirement. The absence of any note on unpaginated vs. bounded results is a minor residual gap.

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%, with both preset_id and include_retired fully documented in the input schema. The description adds no filtering semantics of its own, so the baseline of 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?

Names a specific verb and resource ("List signed decoration-preset releases") and adds the practical payoff — retrieving the id needed for an apply step. It distinguishes itself implicitly from sibling listers like list_decoration_preset_versions by emphasizing signed releases, though it never names an alternative outright.

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 phrase "the id needed to apply one" hints at the workflow context (feed the result into apply_decoration_preset), and "Needs Kiln Pro" is a real gating prerequisite. But it never states when to choose this over list_decoration_preset_versions, list_decoration_preset_branches, or list_decoration_presets, so the agent must infer selection.

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