Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_pull_feature_branch

Destructive

Pull a feature branch’s new versions from a remote into the local feature to keep that branch caught up.

Instructions

Pull one feature 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": {
      "feature_id": "<feature_id>"
    },
    "name": "cloud_pull_feature_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.
feature_idYesThe local feature 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 / feature_id / description
      Added value: +"The local feature 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false, and destructiveHint=true, so the safety profile is partly covered. The description adds useful licensing context with 'Needs Kiln Pro', but it does not explain what local state the destructive pull may overwrite or how conflicts are handled.

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?

The description is two short sentences with no filler and the action is front-loaded. The prerequisite sentence also earns its place, though the overall structure is extremely sparse.

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?

The schema and annotations cover parameter meaning and the destructive nature of the operation fairly well. The description still leaves gaps around conflict behavior, local branch impact, and routing between the multiple branch-pull tools, which matters for a destructive pull operation.

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 all four parameters are already documented in the schema. The description does not add meaning about remote alias selection, feature_id use, or the branch_id versus branch_name choice, so it remains at the schema-backed 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?

The description uses a specific verb, 'Pull', and a specific resource, 'one feature branch's new versions', with the source 'from a remote'. It is clear what the tool does, although it does not explicitly name sibling tools such as cloud_pull_branch or cloud_pull_preset_branch to sharpen the distinction.

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 only guidance is the prerequisite 'Needs Kiln Pro'. There is no explanation of when to use this tool instead of cloud_pull_branch, cloud_pull_preset_branch, or cloud_sync_now, and no when-not 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