Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_pull_preset_branch

Destructive

Pulls new versions of a decoration-preset branch from a remote into the local preset so it catches up with upstream changes. Requires Kiln Pro.

Instructions

Pull one decoration-preset branch's new versions from a remote.

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_pull_preset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNoRemote alias, as registered with ``cloud_remote_add`` (default: ``"default"``). Default: "default".
branch_idNoThe branch to pull, by id. This or ``branch_name`` is required; neither is refused.
preset_idYesThe local decoration preset whose branch to catch up.
branch_nameNoThe branch to pull, by name, when no ``branch_id`` is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / branch_id / description
      Added value: +"The branch to pull, by id.  This or ``branch_name`` is required; neither is refused."
    • addedInput schema / properties / branch_name / description
      Added value: +"The branch to pull, by name, when no ``branch_id`` is given."
    • addedInput schema / properties / preset_id / description
      Added value: +"The local decoration preset whose branch to catch up."
    • changedInput schema / properties / remote / description
      Previous value: -"Default: \"default\"."New value: +"Remote alias, as registered with ``cloud_remote_add`` (default: ``\"default\"``). Default: \"default\"."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and 'pull new versions' is consistent with that mutation profile, so no contradiction. The description does add the Kiln Pro entitlement requirement, but it never explains what local state is overwritten or fast-forwarded, how divergence or conflicts are handled, or whether uncommitted work is at risk.

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 with the action front-loaded and the entitlement caveat separated out. Nothing is padded and nothing needs trimming.

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?

With full schema coverage and no output schema, the definition covers the essentials for a targeted pull: which preset, which branch, which remote, plus the license gate. The remaining gap is conflict and overwrite behavior, which matters for a destructive tool but is a narrower miss than in a bare definition. No output schema exists to defer return-value documentation to, so the description carries slightly more burden than it does.

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%, so remote, branch_id, branch_name and preset_id are each documented in the schema, including the branch_id/branch_name precedence. The description adds no semantics beyond that baseline.

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 (pull), a specific resource (one decoration-preset branch's new versions) and the source (a remote). That scope is narrow enough to separate it from cloud_push_preset_branch, cloud_pull_branch and cloud_pull_feature_branch, 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?

The only guidance is the prerequisite 'Needs Kiln Pro', which is genuinely useful but gating rather than directional. It never says when to pick this over cloud_pull_branch or cloud_pull_feature_branch, nor what precondition the local branch must be in.

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