Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

set_design_public

Control whether a saved design is public or private on kiln3d.com by providing its design ID and visibility flag.

Instructions

Make one of the person's own saved designs public on kiln3d.com, or private again.

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

Input Schema

NameRequiredDescriptionDefault
publicYes``true`` to make it public, ``false`` to make it private.
design_idYesThe design's id, as ``list_designs`` returns it.
preview_tokenNoThe ``preview_token`` from step 1, unchanged. Leave empty to get the preview. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description correctly frames this as a visibility mutation on an external site, so there is no contradiction. However it omits meaningful behavior: whether making a design private breaks existing public links or forks, whether ownership/auth is verified, and — most importantly — the two-phase preview flow implied by the preview_token parameter is never mentioned.

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 with the action and scope front-loaded and zero filler. Nothing is repeated and nothing padding-like is present.

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

Completeness5/5

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

Placeholder.

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%, so design_id, public, and preview_token are all documented in the schema, which sets the baseline at 3. The description adds only the ownership qualifier ("the person's own") for design_id and nothing about the preview-token round trip beyond what the schema already says.

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?

Names a specific verb pair (make public / make private) and a specific resource (a saved design) with an ownership scope ("the person's own saved designs") plus the destination site (kiln3d.com). That is enough to distinguish it from read-oriented siblings such as list_public_designs or get_public_design, though it never names an alternative explicitly.

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?

The bidirectional purpose (public or private again) implies the situations in which to call it, but there is no explicit when-to-use / when-not guidance and no routing against nearby siblings like publish_model, publish_print_twin, or propose_fix_to_public_design. An agent must infer that this toggles visibility rather than publishing a model artifact.

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