Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

save_custom_palette

Destructive

Save a reusable custom color palette by name and assign it to a texture so colors stay consistent across designs.

Instructions

Save a custom color palette for reuse with any texture.

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": {
      "name": "<name>",
      "colors": "<colors>"
    },
    "name": "save_custom_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name for this palette.
colorsYesList of colors — hex (``"#FF0000"``) or named (``"baby blue"``, ``"salmon"``, ``"forest green"``).
textureNoOptional texture this palette is designed for. Default: "any".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / colors / description
      Added value: +"List of colors — hex (``\"#FF0000\"``) or named (``\"baby blue\"``, ``\"salmon\"``, ``\"forest green\"``)."
    • addedInput schema / properties / name / description
      Added value: +"Unique name for this palette."
    • changedInput schema / properties / texture / description
      Previous value: -"Default: \"any\"."New value: +"Optional texture this palette is designed for. Default: \"any\"."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only, destructive write. The description adds the Kiln Pro entitlement requirement, which is useful, but it does not explain what the destructive behavior entails (for example, overwriting an existing same-named palette) or what response to expect. With annotations covering the safety profile, 3 is appropriate.

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, front-loaded with the core action and including a brief prerequisite. There is no redundant wording.

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 simple 3-parameter save tool with full schema coverage and annotations, the description covers purpose and entitlement. However, because annotations flag it destructive, the description should clarify duplicate-name/overwrite behavior; that gap keeps it at 3.

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%, and the schema itself explains name, colors formats, and optional texture default. The description adds no parameter-specific meaning beyond the general 'reuse with any texture' phrase, so baseline 3 applies.

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 states the specific verb and resource: saving a custom color palette, and adds the reuse scope ('with any texture'). It does not explicitly name sibling tools such as list_custom_palettes or delete_custom_palette, so sibling differentiation is implicit rather than stated.

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 gives a slender usage context ('for reuse with any texture') and a prerequisite ('Needs Kiln Pro'), but does not say when to choose this over apply_* texture tools or list/delete palette tools. No when-not or alternatives are provided.

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