Skip to main content
Glama

fork_public_design

Destructive

Copy a public 3D design into your Kiln account to customize or propose a fix to its owner. Use the design's @username/slug address or page link.

Instructions

Make your own copy of someone's public design, in your Kiln account.

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": {
      "address": "<address>"
    },
    "name": "fork_public_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe design's address, as its page shows it: ``@username/slug``, or the page's kiln3d.com link.
to_proposeNo``True`` for a copy made to propose a fix back to the owner; ``False`` (the default) for a copy you keep. Default: false.
make_room_forNoOn a Free plan whose designs are full, the design the person chose to archive so this copy fits. Empty asks nothing. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations mark destructiveHint=true, but the description never explains what is destructive — the make_room_for archiving of an existing design on a full Free plan is only revealed in the schema. With annotations supplying a safety signal, the description should have added the quota/archiving context rather than omitting it entirely.

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 short sentence, front-loaded with the verb and scope, with no filler. It is efficient but so terse that it omits behaviorally important detail.

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 mutation tool flagged destructive, with no output schema, the description leaves out the archiving side effect and the propose-copy variant. The schema covers the mechanics, but the description does not prepare an agent for the destructive case.

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 the baseline is 3. The description adds no parameter meaning beyond the schema and does not explain the propose-vs-keep distinction that to_propose governs.

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 and resource ('Make your own copy of someone's public design') and ties it to the caller's Kiln account, which separates it from get_public_design and list_public_designs. It does not explicitly distinguish itself from propose_fix_to_public_design or keep_proposal_copy, which overlap in intent.

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 and no alternatives named. Nothing tells the agent when to fork versus call propose_fix_to_public_design, or when to set to_propose=true versus keeping the copy, even though siblings cover both cases.

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