Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

build_parametric_prompt

Read-only

Creates an enhanced prompt that guides AI to generate editable, well-structured parametric OpenSCAD code with named variables, comments, and material-aware design limits.

Instructions

Build a prompt optimized for parametric OpenSCAD code generation.

        Returns an enhanced prompt with OpenSCAD-specific instructions that
        guide AI to produce well-structured parametric code with named
        variables, descriptive comments, and material-aware design limits.

        Use this instead of build_generation_prompt when you want the AI to
        generate editable OpenSCAD code rather than a mesh file.

        Args:
            requirements: Natural language description of the desired part.
            material: Optional material override (e.g. "petg").
            printer_model: Optional printer model ID (e.g. "bambu_a1").

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": {
      "requirements": "<requirements>"
    },
    "name": "build_parametric_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoOptional material override (e.g. "petg").
requirementsYesNatural language description of the desired part.
printer_modelNoOptional printer model ID (e.g. "bambu_a1").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"Optional material override (e.g. \"petg\")."
    • addedInput schema / properties / printer_model / description
      Added value: +"Optional printer model ID (e.g. \"bambu_a1\")."
    • addedInput schema / properties / requirements / description
      Added value: +"Natural language description of the desired part."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / material / default
      Removed value: -null
    • removedInput schema / properties / printer_model / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.3/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 still adds real value by describing what the returned prompt contains (named variables, descriptive comments, material-aware design limits) and what it does not produce (a mesh file). It does not state the exact return type or shape, which keeps it below a 5.

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?

The purpose and the sibling comparison are front-loaded and waste nothing. The trailing Args block largely duplicates the schema descriptions word-for-word, which is mild redundancy but not disruptive enough to undermine the structure.

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?

For a prompt-construction tool with no output schema, the description explains what the produced prompt will contain and which generation path it serves. The only gap is that the return type (plain string vs. structured object) is never stated, so an agent knows the content but not the format of the result.

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 coverage is 100%, so all three parameters are already fully documented in the input schema, and the description's Args block restates them almost verbatim (e.g. material: '"petg"', printer_model: '"bambu_a1"'). The description adds no format rules, valid-value constraints, or interaction between material override and printer_model.

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

Purpose5/5

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

The description opens with a specific verb and artifact: 'Build a prompt optimized for parametric OpenSCAD code generation.' It further specifies that the output is an enhanced prompt carrying OpenSCAD-specific instructions, which distinguishes it from generic prompt builders among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative ('Use this instead of build_generation_prompt') and states the selection condition: editable OpenSCAD code versus a mesh file. An agent can route between the two without inspecting either 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