Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

generate_template_variations

Generate 1–10 variations of a parametric template by sampling parameter values across valid ranges to explore design space or present choices.

Instructions

Generate multiple variations of a parametric template.

        Creates N variations by sampling parameter values across their
        valid ranges.  Useful for exploring design space or offering
        choices to the user.

        :param template_id: Template ID (e.g. ``"phone_stand"``).
        :param variation_count: Number of variations (1-10, default 3).
        :param parameter_ranges: Optional overrides ``{param: [min, max]}``.
        :returns: Dict with list of generated variations and their files.

MAKE DOORS: design_session, Kiln's front door for making an object, is not installed here (signed in to Kiln it runs on Kiln's servers). On this install compile_scad IS the make → preview → iterate loop: make it, show the preview, iterate.

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": {
      "template_id": "<template_id>"
    },
    "name": "generate_template_variations"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesTemplate ID (e.g. ``"phone_stand"``).
variation_countNoNumber of variations (1-10, default 3). Default: 3.
parameter_rangesNoOptional overrides ``{param: [min, max]}``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / parameter_ranges / description
      Added value: +"Optional overrides ``{param: [min, max]}``."
    • addedInput schema / properties / template_id / description
      Added value: +"Template ID (e.g. ``\"phone_stand\"``)."
    • changedInput schema / properties / variation_count / description
      Previous value: -"Default: 3."New value: +"Number of variations (1-10, default 3). Default: 3."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / parameter_ranges / default
      Removed value: -null
    • removedInput schema / properties / variation_count / default
      Removed value: -3
    • addedInput schema / properties / variation_count / description
      Added value: +"Default: 3."
  3. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is known. The description adds real value by disclosing the sampling behavior and the return shape ('Dict with list of generated variations and their files'), but it never says where those files are written, whether they persist, or what the cost of N generations is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core paragraph is front-loaded and efficient, but the :param blocks duplicate schema text that is already at 100% coverage, and the trailing 'MAKE DOORS' note about design_session and compile_scad is unrelated boilerplate that does not describe this tool at all.

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?

With no output schema, the description usefully summarizes the return value, and all three parameters are documented. However, for a generating tool that produces files, it omits what happens to those files and which sibling (e.g. preview or generation_status) an agent should call next, leaving a meaningful gap.

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 baseline is 3. The :param lines in the description are verbatim restatements of the schema property descriptions, adding no extra meaning about range semantics, defaulting behavior, or how parameter_ranges keys must match the template's parameters.

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 names a specific verb and resource ('Generate multiple variations of a parametric template') and explains the mechanism ('sampling parameter values across their valid ranges'), which is more than the title alone conveys. It does not explicitly distinguish itself from close siblings such as generate_from_template, optimize_template_params, or smart_generate_from_template, so an agent still has to infer which applies.

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?

'Useful for exploring design space or offering choices to the user' implies the use case but never states when to prefer this over generating a single design from the same template or over optimizing parameters directly. There are no exclusions or prerequisite statements.

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