Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

generate_technical_drawing

Create dimensioned production drawings from a 3D model, exporting PNG, PDF, or DXF sheets with title blocks for manufacturing and documentation.

Instructions

Generate a dimensioned production drawing from a 3D model.

Needs Kiln Business.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_technical_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoSheet title. Defaults to the source file stem. Default: "".
formatsNoOutput formats — any of ``"png"``, ``"pdf"``, ``"dxf"``. Defaults to all three.
materialNoMaterial for the title block (e.g. ``"PETG"``). Default: "".
standardNoDrawing-standard key. ``"house_style"`` (the default) is Kiln's own sheet, which claims no published standard. Other keys belong to registered industry verticals and are refused when the account does not hold that vertical. Default: "house_style".
design_idNoA design Kiln filed (see ``list_designs``). Unlocks the as-built CAD dimensions above. A design with no CAD plan (photo relief, imported mesh) or a machine without the CAD kernel falls through to the paths below, with the reason in ``notes`` — never a guessed number. Default: "".
scad_paramsNoThe design's parameters (name → number). Present ⇒ the exact, parameters-first path. Omit for an imported mesh.
source_pathNoPath to the STL / 3MF / OBJ to draw. Optional when ``design_id`` is given — the design names its own mesh. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"A design Kiln filed (see ``list_designs``). Unlocks the as-built CAD dimensions above.  A design with no CAD plan (photo relief, imported mesh) or a machine without the CAD kernel falls through to the paths below, with the reason in ``notes`` — never a guessed number. Default: \"\"."
    • addedInput schema / properties / formats / description
      Added value: +"Output formats — any of ``\"png\"``, ``\"pdf\"``, ``\"dxf\"``.  Defaults to all three."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Material for the title block (e.g. ``\"PETG\"``). Default: \"\"."
    • addedInput schema / properties / scad_params / description
      Added value: +"The design's parameters (name → number). Present ⇒ the exact, parameters-first path.  Omit for an imported mesh."
    • changedInput schema / properties / source_path / description
      Previous value: -"Default: \"\"."New value: +"Path to the STL / 3MF / OBJ to draw. Optional when ``design_id`` is given — the design names its own mesh. Default: \"\"."
    • changedInput schema / properties / standard / description
      Previous value: -"Default: \"house_style\"."New value: +"Drawing-standard key.  ``\"house_style\"`` (the default) is Kiln's own sheet, which claims no published standard.  Other keys belong to registered industry verticals and are refused when the account does not hold that vertical. Default: \"house_style\"."
    • changedInput schema / properties / title / description
      Previous value: -"Default: \"\"."New value: +"Sheet title.  Defaults to the source file stem. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent already knows this writes something without destroying data. The description adds one genuinely new behavioral fact beyond the annotations: the Kiln Business entitlement gate. It says nothing about where the drawing is written, whether it is idempotent, or what happens when the CAD kernel or vertical is unavailable.

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?

Two sentences, purpose front-loaded, zero filler. The entitlement constraint is separated onto its own line so it reads as a gate rather than part of the action.

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 7-parameter tool with a nested object and no output schema, the description is thin: it never states that the result is a drawing artifact retrievable via list_technical_drawings, nor how the design/SCAD/mesh paths differ. The rich schema compensates for parameter detail, but the overall workflow context is left to the agent to infer.

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% and each parameter already carries substantial documentation (format list, standard-key semantics, design_id fallback behavior, scad_params path switch). The description adds no parameter meaning at all, so the baseline 3 for a fully-covered schema is correct.

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?

"Generate a dimensioned production drawing from a 3D model" names a specific verb (generate), a specific artifact (dimensioned production drawing) and its input (3D model). The sibling list_technical_drawings is implicitly distinguished by the create-vs-list verb, but the description never names it 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?

"Needs Kiln Business" gives a real prerequisite (paid tier required), which is more than most definitions offer. However, it never explains when to choose this over list_technical_drawings, nor which of the three mutually exclusive input paths (design_id, source_path, scad_params) an agent should pick — that choice is left entirely to the schema.

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