Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unarchive_design

Destructive

Restore a previously archived design to default listings by its design_id, so agents can access and manage designs that were hidden from active views.

Instructions

Restore a previously-archived design to default listings.

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": "unarchive_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe id of the archived design to restore, as ``list_designs(filter="archived")`` returns it.

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 archived design to restore, as ``list_designs(filter=\"archived\")`` returns it."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the mutation profile is covered. The description adds the post-condition that the design returns to default listings, but says nothing about required permissions, idempotency, or what happens if the design is not archived.

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?

A single well-formed sentence with the action front-loaded and no filler. It is efficient, though it is arguably too spare for a state-changing operation rather than verbose.

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 one-parameter, well-annotated tool with no output schema, the description covers the essential action and result. Gaps remain around error conditions and side effects, which an agent would need when calling a destructive-flagged operation.

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 design_id field already explains how to obtain the id via list_designs(filter="archived"). The description adds no additional parameter meaning, so the baseline of 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 gives a specific verb and resource ("Restore a previously-archived design") plus the outcome ("to default listings"), which is clearly the inverse of archive_design. It does not explicitly name the sibling it complements, so it stops short of full differentiation.

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 it applies to designs currently in the archived state. There is no explicit statement of prerequisites (e.g. the design must be archived first) or of alternatives such as re-creating or unarchiving via another path.

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