Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

render_design_mesh

Read-only

Force a cached render of a single STL or 3MF mesh with optional color and angle views to preview a design before slicing or printing. Requires Kiln Pro.

Instructions

Force a render of a single mesh through the cache.

Needs Kiln Pro.

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": "render_design_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex color override (e.g. ``"#6E7E8C"``). Default: "".
anglesNoList of angle names (default: ``["iso"]``).
mesh_pathYesPath to the STL/3MF file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / angles / description
      Added value: +"List of angle names (default: ``[\"iso\"]``)."
    • changedInput schema / properties / color / description
      Previous value: -"Default: \"\"."New value: +"Hex color override (e.g. ``\"#6E7E8C\"``). Default: \"\"."
    • addedInput schema / properties / mesh_path / description
      Added value: +"Path to the STL/3MF file."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely new facts beyond that: the render is forced through the cache (cache-bypass behavior) and it requires a Kiln Pro entitlement, which is exactly the kind of gating context an agent needs.

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 short sentences, front-loaded with the action and followed by the entitlement constraint. Nothing is wasted, though 'Needs Kiln Pro' is terse enough to be slightly cryptic about what happens without it.

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 3-parameter tool with annotations and no output schema, the description covers the action and the entitlement gate. It does not indicate what a render produces (file path, image, cache entry) or where the result surfaces, which leaves a real gap for an agent deciding what to do next.

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%, with color, angles and mesh_path all documented in the schema itself. The description adds no meaning about parameter interaction or defaults, so the 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?

States a specific verb and resource ('render of a single mesh') plus a distinguishing mechanism ('through the cache'), which separates it from siblings like compare_renders or preview_decorated_mesh. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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?

'Force' implies bypassing a cached result, and 'Needs Kiln Pro' gives a prerequisite, so usage is implied. There is no explicit statement of when to use this versus prune_design_render_cache or the preview/compare render tools.

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