Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

sign_decoration_preset_release

Create an immutable, Ed25519-signed release for a decoration preset version, using a unique release name to prevent duplicates. Requires Kiln Pro.

Instructions

Designate an immutable Ed25519-signed preset release.

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_version_id": "<preset_version_id>",
      "release_name": "<release_name>"
    },
    "name": "sign_decoration_preset_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
signed_byNoWho signs. Omit it to use the caller's own identity: on Kiln's servers the signed-in account (a different name is refused), locally the declared operator or the computer's user name.
release_nameYesThe release name (e.g. ``1.0.0``). A name already used for this preset is refused (``RELEASE_EXISTS``).
preset_version_idYesId of the preset version to release. An image-family version with no attached image is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / preset_version_id / description
      Added value: +"Id of the preset version to release.  An image-family version with no attached image is refused."
    • addedInput schema / properties / release_name / description
      Added value: +"The release name (e.g. ``1.0.0``).  A name already used for this preset is refused (``RELEASE_EXISTS``)."
    • addedInput schema / properties / signed_by / description
      Added value: +"Who signs.  Omit it to use the caller's own identity: on Kiln's servers the signed-in account (a different name is refused), locally the declared operator or the computer's user name."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world write. The description adds two traits the annotations do not carry: the release becomes immutable, and the operation requires a Kiln Pro entitlement. It omits what happens on success (a signature artifact? a new release record?).

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, action first and prerequisite second, with zero filler. Every sentence earns its place.

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 moderate-complexity mutation with no output schema, the definition covers eligibility and immutability but not the result of signing or the relationship to verification/retirement tools. An agent knows enough to call it but not enough to plan around it.

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 each parameter already documents its own semantics (signer identity fallback, RELEASE_EXISTS refusal, image-family refusal). The description adds no parameter meaning 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?

States a specific verb and resource: 'Designate an immutable Ed25519-signed preset release.' The resource qualifier ('preset release') plus the signing mechanism clearly separates it from sign_design_release and sign_feature_release, though it never names those siblings explicitly.

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 one real prerequisite, which is useful for eligibility. But there is no guidance on when to sign a release versus verify_decoration_preset_release, cloud_push_preset_release, or retire_decoration_preset_release, nor on when signing should be skipped.

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