Skip to main content
Glama

sign_decoration_preset_release

Designate an immutable Ed25519-signed preset release to lock decoration presets for 3D printing, enabling tamper-proof versioning. Requires Kiln Pro.

Instructions

Designate an immutable Ed25519-signed preset release.

Everything in Free, plus calibration that learns your printer, mid-print edits, and unlimited textures and decorations. Requires Kiln Pro. Upgrade: https://kiln3d.com/pricing?src=agent&tool=sign_decoration_preset_release

Input Schema

NameRequiredDescriptionDefault
signed_byNo
release_nameYes
preset_version_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description does disclose meaningful behavior: the release is immutable and Ed25519-signed, and Kiln Pro is required. However, it does not explain permissions, side effects, return behavior, or whether signing is idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but more than half the description is promotional upgrade text unrelated to helping an agent invoke the tool correctly. Those sentences do not earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter signing tool with no annotations and no output schema, the description is missing parameter meaning, usage context, and behavioral details. The Kiln Pro prerequisite helps, but the definition remains substantially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain preset_version_id, release_name, or signed_by. The word 'signed' weakly hints at signed_by, but none of the three parameters are meaningfully documented.

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 first sentence gives a specific verb and resource: designating an immutable Ed25519-signed preset release. It is clear what the tool does, but it does not distinguish this from sibling signing tools such as sign_design_release or sign_feature_release.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no alternatives, and no conditions beyond a Kiln Pro requirement. The remaining text is marketing/upsell rather than invocation guidance.

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