Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

push_palettes_to_cloud

Destructive

Upload locally saved custom palettes to your Kiln Pro cloud account so they sync across devices and remain available for future 3D printing projects.

Instructions

Push locally saved custom palettes to your cloud account.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "push_palettes_to_cloud"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating, potentially destructive operation; the description says nothing about what that destruction means. It never states whether existing cloud palettes are overwritten, merged, or duplicated, nor whether the push is idempotent. The Kiln Pro prerequisite is the only behavior-level detail added beyond structured data.

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 lines with the action front-loaded and the prerequisite separated out. Every sentence carries information and nothing is padded.

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 zero-argument operation with no output schema, the description covers the essentials of what is invoked, but leaves the most consequential question unanswered: what happens to palettes already in the cloud account. Given destructiveHint=true, that omission is material rather than cosmetic.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter omissions exist to penalize.

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 and resource ("push locally saved custom palettes") plus the destination ("your cloud account"), which is far clearer than the bare name. It does not distinguish itself from nearby cloud-upload siblings such as cloud_push_preset_branch or push_reflog_to_cloud, so an agent must still infer that this tool is specifically palette-scoped.

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?

"Needs Kiln Pro" supplies a real prerequisite that gates invocation, which is more than most definitions offer. However, there is no explicit when-to-use framing (e.g. after save_custom_palette, before switching machines) and no mention of alternatives such as keeping palettes local.

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