Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_decoration_preset_versions

Read-only

List all saved versions of a specified decoration preset, oldest first, to inspect its revision history. Requires Kiln Pro.

Instructions

List every saved version of one decoration preset, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
preset_idYesThe stable preset id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / preset_id / description
      Added value: +"The stable preset id."
  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 readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two pieces beyond that: the result ordering (oldest first) and the Kiln Pro entitlement requirement, both of which affect whether and how the agent calls it. Return shape and pagination remain unstated.

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 no filler; the scope and ordering come first and the entitlement caveat second. Every sentence carries 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 read-only, single-parameter listing tool with no output schema, the definition covers scope, ordering and tier gating. What a 'version' contains and whether results are paginated are not covered, but these are minor for a list call whose annotations already signal a safe read.

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% and the single parameter is documented as 'The stable preset id.' The description only restates that one preset is targeted and adds no format, id-source, or error semantics beyond the schema, 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 — 'List every saved version of one decoration preset' — plus the ordering ('oldest first'). It is not distinguished from nearby siblings such as list_decoration_preset_branches and list_decoration_preset_releases, so an agent cannot be certain which lineage concept this returns without opening the schema.

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 prerequisite 'Needs Kiln Pro' tells the agent when the tool is callable, which is useful gating information. However, there is no guidance on when to prefer this over the sibling branch/release listings or what to do when the tier check fails.

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