Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_push_preset_release

Pushes a locally signed decoration-preset release to a remote, enabling distribution through Kiln Pro.

Instructions

Push a locally-signed decoration-preset 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_preset_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNoRemote alias, as registered with ``cloud_remote_add`` (default: ``"default"``). Default: "default".
release_idYesThe id of the locally signed decoration-preset 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 decoration-preset 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 establish that this is a non-read-only, non-destructive, non-open-world operation. The description adds the Kiln Pro requirement, but does not disclose conflict behavior, authentication needs, or what happens to the remote when the push occurs.

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 no wasted wording. The core action is front-loaded and the prerequisite follows immediately.

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 mutation tool with annotations and complete schema descriptions, the definition covers the essential action and prerequisite. Only minor behavioral details, such as failure or conflict handling, are absent.

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 the schema fully documents both release_id and remote. The description adds no parameter meaning beyond what the input schema already provides.

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 and resource: pushing a locally-signed decoration-preset release to the remote. This distinguishes it from generic release-pushing siblings, though it does not explicitly name those alternatives.

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 'Needs Kiln Pro' prerequisite gives useful context for when the tool can be used, but there is no explicit guidance on when to choose this over cloud_push_release or other push tools, nor any 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