Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

archive_design

Destructive

Hide a design from default listings while preserving every version, branch, recipe sidecar, and print outcome for later recovery.

Instructions

Archive a design — hide from default listings while preserving every version, branch, recipe sidecar, and print outcome.

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": {
      "design_id": "<design_id>"
    },
    "name": "archive_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe id of the design to archive, as ``list_designs`` returns it. A design not in the caller's library is ``NOT_FOUND``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"The id of the design to archive, as ``list_designs`` returns it.  A design not in the caller's library is ``NOT_FOUND``."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description carries a lighter burden. It still adds real context by enumerating what is preserved (versions, branches, recipe sidecar, print outcomes), clarifying that the destructive hint applies to listing visibility rather than data loss. It does not mention permission requirements or how to reverse the action.

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?

A single sentence that front-loads the action and spends its remaining words on the non-obvious preservation guarantee. Nothing is redundant or padded.

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 one-parameter mutation with full schema coverage, complete annotations, and no output schema, the definition supplies what an agent needs: the visibility effect and the preservation guarantee. A pointer to unarchive_design as the inverse would make it complete.

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%: the design_id description already covers the required id format and the NOT_FOUND behavior. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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 ('Archive a design') and adds the effect ('hide from default listings'), which tells an agent exactly what changes. It does not explicitly contrast with delete_design or unarchive_design, so the sibling differentiation is left implicit.

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?

Usage is only implied: an agent can infer archiving is the reversible alternative to delete_design and that unarchive_design reverses it, but neither alternative nor a when-to-use condition is stated. The NOT_FOUND case is covered by the schema rather than the description.

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