Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

rename_decoration_preset

Destructive

Rename a decoration preset to update its display name across all saved versions while preserving content and history. Requires Kiln Pro.

Instructions

Rename a decoration preset — update the display name across every saved version without touching content or history.

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>",
      "new_name": "<new_name>"
    },
    "name": "rename_decoration_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesNew display name. Whitespace-only names are rejected (``PRESET_VALIDATION``).
preset_idYesThe stable preset id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / new_name / description
      Added value: +"New display name.  Whitespace-only names are rejected (``PRESET_VALIDATION``)."
    • 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?

Beyond the annotations, the description discloses the blast radius (all saved versions), the invariant preserved (content and history untouched), and the entitlement gate (Kiln Pro). The annotations already flag destructiveHint=true and readOnlyHint=false, so this added scoping detail is the right kind of contribution; only the response/error behaviour is left 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 plus a gating note, with the core action and scope front-loaded and zero filler. Every clause carries information an agent needs before calling.

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 mutation with full schema coverage and annotations, the description covers action, scope, side-effect boundaries, and the tier requirement. No output schema exists, so return values need not be explained; only error/response behaviour remains thin.

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 and new_name are both documented in the schema, including the PRESET_VALIDATION rejection for whitespace-only names. The description adds no further parameter-level meaning, 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?

The description names a specific verb and resource ("Rename a decoration preset") and adds scope: the display name is updated "across every saved version." That is enough to separate it from the many other rename_* siblings, but it never explicitly contrasts with the closest neighbour, rename_decoration_preset_branch, so it stops short of full sibling differentiation.

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" gives a concrete prerequisite for calling it, which is real usage context. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as rename_decoration_preset_branch or rename_decoration_preset for branch-scoped renames; the usage condition is only implied by the resource noun.

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