Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_push_feature_release

Push a locally signed feature release to a remote to share or deploy the finalized version; requires Kiln Pro.

Instructions

Push a locally-signed feature release to the 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": {
      "release_id": "<release_id>"
    },
    "name": "cloud_push_feature_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNoRemote alias, as registered with ``cloud_remote_add`` (default: ``"default"``). Default: "default".
release_idYesThe id of the locally signed feature release to push.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / release_id / description
      Added value: +"The id of the locally signed feature release to push."
    • 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 declare non-read-only, non-destructive, closed-world behavior; the description adds the Kiln Pro entitlement and the locally-signed precondition. It does not describe remote-side effects or failure behavior, so it adds useful but limited behavioral context.

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 terse sentences, front-loaded with the action and followed by the entitlement precondition. No redundant wording or structural clutter.

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?

For a simple two-parameter push operation with complete schema descriptions and annotations, the definition covers action, target, signed-state, and entitlement. It omits explicit cross-tool workflow details, but nothing critical to invoking it is missing.

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 coverage is 100%, and both parameters are already documented, including release_id's signed-release meaning and remote's default. The description adds no additional syntax, constraints, or interpretation beyond the schema.

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 ('Push') and resource ('feature release'), qualified as locally-signed and targeting a remote. It implicitly separates this from branch-push and preset-release siblings, though it does not explicitly name or contrast them.

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?

It provides a prerequisite ('Needs Kiln Pro') and implies the release must already be signed, but it does not state when to choose this over cloud_push_release or cloud_push_preset_release, nor explicitly mention signing as a prior step. Usage is inferable but not fully guided.

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