Skip to main content
Glama

smart_generate_from_template

Generate a print-ready 3D model from a parametric template with structural risk analysis and auto-reinforcement. Returns STL path and optimized slicer settings for functional parts.

Instructions

Generate from template + structural analysis + print settings (recommended for functional parts).

        Higher-level than ``generate_from_template`` — adds structural risk analysis
        and auto-reinforcement. This is the **one-step design-to-print-ready** pipeline:

        1. Generates STL from a parametric template (like ``generate_from_template``)
        2. Runs structural risk analysis (thin necks, cantilevers, sharp corners)
        3. Optionally auto-applies reinforcements (fillets, wall thickening, etc.)
        4. Infers optimal slicer settings tuned to the design's structural profile
        5. Returns the STL path + recommended settings ready for slicing

        The agent can take the output and directly call ``reslice_with_overrides``
        or ``run_reslice_and_print`` with the recommended settings.

        :param template_id: Template ID from ``list_design_templates``.
        :param parameters: Parameter overrides (e.g., ``{"phone_width": 80}``).
        :param material: Filament type for settings inference (PLA, PETG, ABS, etc.).
        :param auto_reinforce: If True, auto-apply structural reinforcements.
        :returns: Dict with STL path, structural grade, reinforcements, and print settings.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialNoPLA
parametersNo
template_idYes
auto_reinforceNo
Behavior4/5

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

With no annotations, the description carries full burden. It details the 5-step pipeline (generation, analysis, reinforcement, settings inference, return) and mentions the auto_reinforce option. It does not disclose potential processing time, caching, or side effects, but the core behavior is transparently described.

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 description is well-structured with enumerated steps and bold emphasis for key points. At about 150 words, it is informative without being verbose. Minor redundancy could be trimmed, but overall it is clearly organized and front-loaded with purpose.

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?

Given the tool's complexity and lack of output schema, the description covers the pipeline, parameter meanings, return types, and sibling relationship. Missing error handling or failure modes, but for a design tool without output schema, it provides sufficient contextual completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds significant meaning: it explains template_id comes from `list_design_templates`, parameters are optional overrides (with example `{"phone_width": 80}`), material is for settings inference, and auto_reinforce toggles reinforcements. This fully compensates for the bare schema.

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 clearly states the tool generates STL from a parametric template with added structural analysis and print settings. It explicitly distinguishes itself from the sibling `generate_from_template` by noting it is higher-level and includes risk analysis and auto-reinforcement, providing a 'design-to-print-ready' pipeline.

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

Usage Guidelines4/5

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

The description recommends use for functional parts and positions this tool as more advanced than `generate_from_template`. It outlines the output can be used with `reslice_with_overrides` or `run_reslice_and_print`. However, it does not explicitly state when to avoid this tool (e.g., for simple shapes) or list prerequisites beyond having a template ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server