Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

keep_design

Capture your designed 3D model from Kiln's servers. Export the full-quality file to your local machine for slicing, printing, or detailed inspection.

Instructions

Keep a make that Kiln's servers built: save its file to this computer.

    A make from one of Kiln's served tools (a coaster, a textured part,
    a decorated model) is built on Kiln's servers and shown on the
    stage.  Looking at it and changing it are free.  Call this when the
    user wants to KEEP it: to slice, print or export it.  It saves the
    full-quality file on this computer and returns its path
    (``mesh_path``), which every local tool takes.

    On the Free plan a keep counts toward that kind of make's monthly
    allowance, and the answer says how many are left (``keep``).  Paid
    plans keep without limit.  A make is only ever counted once.

    Args:
        artifact_token: The token of the make to keep.  It is in the
            make's own answer, under ``made_on_kiln_servers``.

Input Schema

NameRequiredDescriptionDefault
artifact_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behavior: full-quality local file saving, returned mesh_path, Free-plan quota counting, remaining keep count, paid unlimited keeps, and once-only counting. It does not cover auth requirements, overwrite behavior, or local filesystem side effects.

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?

The description is front-loaded with the core action and then adds usage, billing, and parameter details in a logical order. It is somewhat long, but nearly every sentence earns its place by clarifying behavior an agent needs.

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?

Given no annotations, no output schema, and a billing-sensitive one-parameter operation, the description is complete enough to call correctly: it explains the action, when to use it, the return path, and quota implications. Minor gaps remain around permissions and error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, but the description explains that artifact_token identifies the make to keep and where to find it: in the make answer under made_on_kiln_servers. It could add token format details, but it compensates well for the schema gap.

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 states a specific verb and resource: keep a make built on Kiln's servers and save its file to this computer. It distinguishes keeping from merely looking at or changing a make, though it does not explicitly name sibling tools such as keep_painted_detail.

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

Usage Guidelines4/5

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

It clearly says to call this when the user wants to keep a make for slicing, printing, or exporting, and notes that viewing and changing are free. It does not name alternative tools or spell out when not to use this tool, but the usage context is clear.

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