Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_clone_preset

Creates local storage by cloning a remote-only decoration preset so it can be used locally; requires Kiln Pro.

Instructions

Bootstrap local storage for a remote-only decoration preset.

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

Input Schema

NameRequiredDescriptionDefault
remoteNoRemote alias (default: ``"default"``). Default: "default".
preset_idYesThe decoration-preset identifier to clone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / preset_id / description
      Added value: +"The decoration-preset identifier to clone."
    • changedInput schema / properties / remote / description
      Previous value: -"Default: \"default\"."New value: +"Remote alias (default: ``\"default\"``). Default: \"default\"."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already state this is a non-read-only, non-destructive, closed-world write. The description adds one genuinely useful piece of context not in the annotations: the 'Needs Kiln Pro' entitlement gate. However, for a write that creates local storage it says nothing about what happens if the preset already exists locally (overwrite, merge, or fail), which is exactly the behavioral risk an agent needs to know.

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, front-loaded with the action and resource before the prerequisite. The trailing 'Needs Kiln Pro.' fragment is abrupt but carries real information, so nothing is wasted — it just reads as a terse note rather than structured guidance.

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 clone operation with no output schema and annotations covering the safety profile, the definition covers the essentials. It is nonetheless silent on failure/idempotency behavior and on the relationship to the cloud_pull_* and cloud_clone_* siblings, leaving gaps an agent may hit at invocation time.

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%, with both remote (default 'default') and preset_id documented in the schema itself. The description adds no syntax, format, or source-location detail beyond what the schema already provides, 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?

Names a specific verb ('Bootstrap local storage') and a specific resource object ('a remote-only decoration preset'), which is clearly distinguishable from the many decoration/preset listing and creation siblings. It stops short of explicitly contrasting with its nearest siblings (cloud_clone_design, cloud_clone_feature, cloud_pull_preset_branch), so differentiation is by noun only.

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?

'remote-only decoration preset' implies the triggering condition (the preset exists only in the cloud, not locally), but the agent must infer it. No alternative is named — notably not cloud_pull_preset_branch, which an agent could easily confuse with this tool — and no when-not guidance is given.

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