Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

auto_generate_manual_for_print

Triggers automatic generation of a PDF manual for a multi-part 3D print assembly, allowing language, branding, and background render options.

Instructions

Fire the automatic manual trigger for a multi-part print (Business+).

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": {
      "assembly_json": "<assembly_json>"
    },
    "name": "auto_generate_manual_for_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandingNo``"prominent"``, ``"subtle"``, ``"white_label"``, or omitted / ``"auto"`` to resolve from the caller's plan.
languagesNoOrdered list of language codes (e.g. ``["en", "de"]``). Omitted, the manual is English only; unsupported codes fall back to English.
backgroundNo``True`` (default) renders in the background and returns at once with ``pending=True``; ``False`` waits for the render inline. Default: true.
output_dirNoDirectory to write the PDF into. Omitted, the manual is written to Kiln's manual cache folder for this assembly.
design_nameNoCover-page title; falls back to the assembly's own ``name``.
assembly_jsonYesRequired. The assembly state, as a JSON string or object, as ``create_assembly`` / ``add_assembly_part`` / ``add_assembly_interface`` return it. A one-part assembly is skipped.
co_brand_nameNoWhen set, the cover reads "Made by ``co_brand_name``" instead of the Kiln wordmark.
cover_languageNoLanguage for the cover; defaults to ``languages[0]`` or English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • addedInput schema / properties / assembly_json / description
      Added value: +"Required. The assembly state, as a JSON string or object, as ``create_assembly`` / ``add_assembly_part`` / ``add_assembly_interface`` return it. A one-part assembly is skipped."
    • changedInput schema / properties / background / description
      Previous value: -"Default: true."New value: +"``True`` (default) renders in the background and returns at once with ``pending=True``; ``False`` waits for the render inline. Default: true."
    • addedInput schema / properties / branding / description
      Added value: +"``\"prominent\"``, ``\"subtle\"``, ``\"white_label\"``, or omitted / ``\"auto\"`` to resolve from the caller's plan."
    • addedInput schema / properties / co_brand_name / description
      Added value: +"When set, the cover reads \"Made by ``co_brand_name``\" instead of the Kiln wordmark."
    • addedInput schema / properties / cover_language / description
      Added value: +"Language for the cover; defaults to ``languages[0]`` or English."
    • addedInput schema / properties / design_name / description
      Added value: +"Cover-page title; falls back to the assembly's own ``name``."
    • addedInput schema / properties / languages / description
      Added value: +"Ordered list of language codes (e.g. ``[\"en\", \"de\"]``). Omitted, the manual is English only; unsupported codes fall back to English."
    • addedInput schema / properties / output_dir / description
      Added value: +"Directory to write the PDF into. Omitted, the manual is written to Kiln's manual cache folder for this assembly."
  2. Addedv1.5.0

TDQS

C2.8/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, so the write-but-non-destructive profile is covered. The description adds one genuinely useful behavioral fact — the Business+ plan requirement — but omits that this renders and writes a PDF, that rendering can be backgrounded and return pending=True, and that one-part assemblies are silently skipped.

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 sentence with no padding and the key qualifier (Business+) placed where it will be read. It is efficient, though the terseness borders on under-specification rather than deliberately restrained conciseness.

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

Completeness2/5

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

For an eight-parameter tool that renders and writes a PDF, has a background mode, and lives among several near-identical manual tools with no output schema, one sentence is not enough. An agent cannot tell from this description which manual-generation sibling to select or what it will get back.

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 every parameter including assembly_json, branding, background, and output_dir is already documented in the schema, and the description adds no semantics beyond it. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is metaphorical ("Fire the ... trigger") and the object is described as an "automatic manual trigger" rather than as producing a print manual PDF, so the actual effect must be inferred from the schema. It also fails to distinguish itself from the very close sibling generate_assembly_manual, which a reader would reasonably assume does the same thing.

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?

The only guidance is the parenthetical "(Business+)" plan gate, which is a licensing prerequisite rather than a when-to-use rule. There is no statement of when to call this versus generate_assembly_manual, diff_assembly_manuals, embed_manual_in_3mf, or batch_verify_manuals, all of which sit in the same manual-related cluster.

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