Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

inspect_design

Render and analyze a 3D mesh to produce shaded previews, cross-section slices, measurements, and an optional print-readiness verdict in a manifest bundle.

Instructions

Render and analyze a 3D mesh — shaded previews, cross-section slices, raw measurements (volume, watertightness, dimensions), and an optional print-readiness verdict. Channels are opt-in, results land in a manifest.json bundle.

Free accounts get 3 inspections a month; Pro has no monthly limit.

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": {
      "mesh_path": "<mesh_path>"
    },
    "name": "inspect_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsNoChannel names to run. Defaults to ``["rgb"]``. Call with an unknown channel to get the available list.
mesh_pathYesPath to the STL/3MF/OBJ mesh to inspect.
bundle_dirNoOutput directory. A fresh temp dir when blank; a named one must be new or empty (``OUTPUT_EXISTS`` otherwise), so an earlier bundle is never written over. Default: "".
product_typeNoOptional product slug (e.g. ``"frisbee"``). When Kiln has angle knowledge for it, channels render the right views for that product, not the generic set. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / bundle_dir / description
      Previous value: -"Default: \"\"."New value: +"Output directory. A fresh temp dir when blank; a named one must be new or empty (``OUTPUT_EXISTS`` otherwise), so an earlier bundle is never written over. Default: \"\"."
    • addedInput schema / properties / channels / description
      Added value: +"Channel names to run. Defaults to ``[\"rgb\"]``. Call with an unknown channel to get the available list."
    • addedInput schema / properties / mesh_path / description
      Added value: +"Path to the STL/3MF/OBJ mesh to inspect."
    • changedInput schema / properties / product_type / description
      Previous value: -"Default: \"\"."New value: +"Optional product slug (e.g. ``\"frisbee\"``). When Kiln has angle knowledge for it, channels render the right views for that product, not the generic set. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false with destructiveHint=false, which is a confusing combination; the description resolves it by explaining that results are written out as a manifest.json bundle, i.e., it writes output files rather than mutating the mesh. It also discloses account-level rate limits (3 free inspections/month) that annotations cannot convey. It omits runtime cost, whether rendering is GPU/queue-bound, or how long an inspection takes.

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?

Two compact sentences, front-loaded with the verb and output inventory, followed by a short quota note — almost no waste. The 'Channels are opt-in, results land in a manifest.json bundle' clause partially restates schema fields but also carries the transparency payload, so it earns most of its space.

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?

With no output schema, the description correctly tells the agent where results land (manifest.json bundle) and what channels produce, plus the quota constraint. Given four fully documented parameters and safe/non-destructive annotations, this is nearly complete; only runtime/permission expectations for writing the bundle are unstated.

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 four parameters are already fully documented, including the channels default, the bundle_dir must-be-new rule, and the product_type angle-knowledge behavior. The description adds only the high-level framing of opt-in channels and the manifest bundle, which the schema already implies; baseline 3 applies.

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 leads with a concrete verb and resource ('Render and analyze a 3D mesh') and enumerates the concrete outputs (shaded previews, cross-section slices, measurements, print-readiness verdict), so an agent knows exactly what this produces. It stops short of naming or contrasting sibling tools such as render_design_mesh, inspect_mesh_view, cross_section_view, or analyze_printability, leaving overlap for the agent to resolve.

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?

It gives useful operating context — channels are opt-in, unknown channels return the available list, and free-tier quota is 3/month — but never states when to prefer this over the many sibling inspection/rendering tools or when not to use it. Usage is implied by the quota and channel mechanics rather than explicitly scoped.

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