Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

annotate_decoration_preset_branch

Destructive

Set a human-readable purpose annotation on a decoration preset branch so you can document its role; provide an empty string to clear an existing annotation. Requires Kiln Pro.

Instructions

Set the human-readable purpose string for a preset branch.

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": {
      "branch_id": "<branch_id>",
      "annotation": "<annotation>"
    },
    "name": "annotate_decoration_preset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_idYesId of the preset branch to describe.
annotationYesThe purpose text to store on the branch. It replaces any earlier annotation; an empty string clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / annotation / description
      Added value: +"The purpose text to store on the branch.  It replaces any earlier annotation; an empty string clears it."
    • addedInput schema / properties / branch_id / description
      Added value: +"Id of the preset branch to describe."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write, but the description does not explain the consequence: that an existing annotation is overwritten without recovery. The overwrite/clear semantics live only in the schema, and the tool does not say what happens if the branch id is invalid or the user lacks Pro entitlement beyond simply naming the requirement.

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

Conciseness4/5

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

Two short sentences with the core action front-loaded and the entitlement constraint separated. There is no filler, though the second sentence is terse enough to be slightly ambiguous about whether it is a hard error or a warning.

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 simple two-parameter tool with full schema documentation and an entitlement note, most of what an agent needs is present. What is missing is any statement of failure modes or irreversibility, which matters more given the destructiveHint=true annotation.

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 both parameters carry explicit descriptions, including the overwrite and empty-string-clears behavior. The description adds nothing beyond the schema, 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?

The description gives a specific verb ("Set") and object ("human-readable purpose string for a preset branch"), which is distinct from mutating siblings like rename_decoration_preset_branch or retire_decoration_preset_branch. It does not explicitly name those siblings, so the differentiation is implied rather than stated.

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" is a genuine prerequisite that tells the agent when this tool is callable at all, which is useful gating information. However, there is no guidance on when to prefer this over rename_decoration_preset_branch or how it relates to create_decoration_preset_branch — the usage context is only implied.

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