Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

create_design

Creates an empty design slot for a new 3D model in Kiln, giving each project a unique slug and Git-style version history.

Instructions

Create an empty design slot — gh repo create for 3D.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional human-readable display name. Falls back to the slug when empty. Shown in the workshop header and the dashboard list. Default: "".
design_idYesSlug identifier. Must be kebab-case, 1-64 chars, ``[a-z0-9-]`` only, starting with an alphanumeric character. Used as both the filesystem directory name and the workshop URL slug, so it must be unique per user.
descriptionNoOptional one-line description (≤ 280 chars). Surfaces in ``list_designs`` / ``get_design`` and the workshop sidebar. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / description / description
      Previous value: -"Default: \"\"."New value: +"Optional one-line description (≤ 280 chars).  Surfaces in ``list_designs`` / ``get_design`` and the workshop sidebar. Default: \"\"."
    • addedInput schema / properties / design_id / description
      Added value: +"Slug identifier.  Must be kebab-case, 1-64 chars, ``[a-z0-9-]`` only, starting with an alphanumeric character.  Used as both the filesystem directory name and the workshop URL slug, so it must be unique per user."
    • changedInput schema / properties / name / description
      Previous value: -"Default: \"\"."New value: +"Optional human-readable display name.  Falls back to the slug when empty.  Shown in the workshop header and the dashboard list. Default: \"\"."
  2. Addedv1.5.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the notion that the slot starts empty, which is genuinely useful, but says nothing about failure behavior (duplicate design_id, uniqueness per user), side effects on the filesystem/workshop URL, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the verb, which is good, but a substantial share of the limited text is spent on an analogy rather than on information the agent cannot get elsewhere. The metaphor buys intuition at the cost of precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with only three well-documented parameters and no output schema, the description should still say what a caller gets back and what happens when the slug already exists. Neither is covered, and the sibling set is dense enough that the omission matters.

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%, with the kebab-case constraint, length limits, uniqueness requirement, and defaults all documented in the schema. The description adds no parameter meaning at all, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource ("create ... design slot") is present, but the object is described as an "empty design slot" and then only through a metaphor ("gh repo create for 3D"), which implies scaffolding/container creation without stating it plainly. It does not distinguish this from siblings such as create_design_branch, generate_model, or smart_generate_from_template, several of which also "create" design-related artifacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent cannot tell from this text whether create_design should precede generate_model, or how it relates to create_design_branch or design_session.

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