Skip to main content
Glama

delete_custom_palette

Destructive

Delete a saved custom color palette by name; requires Kiln Pro.

Instructions

Delete a saved custom color palette.

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>"
    },
    "name": "delete_custom_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the palette to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / name / description
      Added value: +"Name of the palette to delete."
  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 declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the danger profile is known. The description adds the Pro-tier requirement, which is genuinely beyond the annotations, but says nothing about irreversibility, whether a missing palette errors, or whether the deletion can be undone.

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?

Two short lines with the action stated first and the prerequisite second, with zero filler. The only minor inefficiency is that the tier requirement is a separate fragment rather than integrated into a single sentence.

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 single-parameter destructive tool with no output schema, the description covers the action, the target, and the Pro prerequisite, and the annotations carry the safety profile. What is missing—reversibility and error behavior on an unknown name—is modest for a tool of this complexity.

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?

There is one parameter with 100% schema description coverage ("Name of the palette to delete."), so the schema fully documents the input. The description adds no extra meaning about name matching (case sensitivity, partial matches) beyond what the schema states; 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?

States a specific verb ("Delete") and a specific resource ("a saved custom color palette"), which cleanly separates it from the save/list/push palette siblings. It does not explicitly name those siblings as alternatives, but the CRUD verb distinction is unambiguous.

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 gating prerequisite that tells the agent when the call is even permitted, which is real usage context. However, there is no guidance on when to prefer this over alternatives, nor what to do if the palette is still referenced elsewhere.

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