Skip to main content
Glama

generate_model

Destructive

Generate a 3D model from a text prompt via external AI APIs; returns a job ID for tracking and download, ideal for custom objects without a template or image.

Instructions

Generate a 3D model from a text prompt via external AI API (Meshy/etc).

        Pass ``material`` when the user has named one ("print this in
        TPU") — it steers the design-intelligence prompt enrichment
        toward that material's constraints.  It is a design hint, not a
        slicing setting; leave it empty when the material is undecided.

        Start here if user has no template/image — just a text description.
        For image-based generation, use ``generate_model_from_image``.
        For parametric templates (local, no AI API needed), use ``generate_from_template``.
        To also slice + upload in one step, use ``generate_and_print``.

        **EXPERIMENTAL:** AI-generated 3D models are experimental and may not
        be suitable for printing without manual review.  Generated geometry
        can have thin walls, non-manifold faces, floating islands, or
        dimensions that exceed printer build volume.  3D printers are delicate
        hardware — always validate the generated mesh before printing.

        **When possible, prefer downloading proven community models from
        marketplaces** (Thingiverse, MyMiniFactory) over generating new ones.
        Use generation for custom/unique objects only.

        Submits a generation job to the specified provider and returns a
        job ID for status tracking.  Use ``generation_status`` to poll for
        completion, then ``download_generated_model`` to retrieve the file.

        **Prompt tips for Meshy (text-to-3D AI):**
        - Describe the physical object clearly: shape, size, purpose.
        - Include material cues: "wooden", "metallic", "smooth plastic".
        - Specify printability: "solid base", "no overhangs", "flat bottom".
        - Keep prompts under 200 words for best results (max 600 chars).
        - Good example: "A phone stand with a curved cradle, flat rectangular
          base, and angled back support. Smooth plastic surface."
        - Bad example: "make me something cool" (too vague).

        **For OpenSCAD**, the prompt must be valid OpenSCAD code.  The job
        completes synchronously and the result is immediately available.

        Args:
            prompt: Text description (or OpenSCAD code for ``openscad``).
            provider: Generation provider: ``"meshy"``, ``"gemini"``,
                ``"tripo3d"``, ``"stability"`` (cloud, each needs its own
                key) or ``"openscad"`` (local, keyless).  Default
                ``"meshy"``.
            format: Desired output format (``"stl"``).  Default: ``"stl"``.
            style: Optional style hint: ``"realistic"`` or ``"sculpture"``
                for ``"meshy"``; ``"organic"``, ``"mechanical"`` or
                ``"decorative"`` for ``"gemini"``.  Ignored by other
                providers.
            material: Material the generated model is meant to print in,
                kept with the result for the slice; ``"PLA"`` by default.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoOptional style hint: ``"realistic"`` or ``"sculpture"`` for ``"meshy"``; ``"organic"``, ``"mechanical"`` or ``"decorative"`` for ``"gemini"``. Ignored by other providers.
formatNoDesired output format (``"stl"``). Default: ``"stl"``. Default: "stl".
promptYesText description (or OpenSCAD code for ``openscad``).
materialNoMaterial the generated model is meant to print in, kept with the result for the slice; ``"PLA"`` by default. Default: "".
providerNoGeneration provider: ``"meshy"``, ``"gemini"``, ``"tripo3d"``, ``"stability"`` (cloud, each needs its own key) or ``"openscad"`` (local, keyless). Default ``"meshy"``. Default: "meshy".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / format / description
      Previous value: -"Default: \"stl\"."New value: +"Desired output format (``\"stl\"``).  Default: ``\"stl\"``. Default: \"stl\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Material the generated model is meant to print in, kept with the result for the slice; ``\"PLA\"`` by default. Default: \"\"."
    • addedInput schema / properties / prompt / description
      Added value: +"Text description (or OpenSCAD code for ``openscad``)."
    • changedInput schema / properties / provider / description
      Previous value: -"Default: \"meshy\"."New value: +"Generation provider: ``\"meshy\"``, ``\"gemini\"``, ``\"tripo3d\"``, ``\"stability\"`` (cloud, each needs its own key) or ``\"openscad\"`` (local, keyless).  Default ``\"meshy\"``. Default: \"meshy\"."
    • addedInput schema / properties / style / description
      Added value: +"Optional style hint: ``\"realistic\"`` or ``\"sculpture\"`` for ``\"meshy\"``; ``\"organic\"``, ``\"mechanical\"`` or ``\"decorative\"`` for ``\"gemini\"``.  Ignored by other providers."
  2. Changed7 schema fields changedv1.5.0
    • removedInput schema / properties / format / default
      Removed value: -"stl"
    • addedInput schema / properties / format / description
      Added value: +"Default: \"stl\"."
    • removedInput schema / properties / material / default
      Removed value: -""
    • addedInput schema / properties / material / description
      Added value: +"Default: \"\"."
    • removedInput schema / properties / provider / default
      Removed value: -"meshy"
    • addedInput schema / properties / provider / description
      Added value: +"Default: \"meshy\"."
    • removedInput schema / properties / style / default
      Removed value: -null
  3. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / material
      Added value: +{
      +  "default": "",
      +  "title": "Material",
      +  "type": "string"
      +}
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, destructive=true, openWorld=false) by disclosing that output is EXPERIMENTAL, that geometry may have thin walls, non-manifold faces, floating islands, or exceed build volume, and that manual validation is required before printing. It also describes the async contract — job ID returned, poll with generation_status, fetch with download_generated_model — and notes the openscad provider is local, keyless, and synchronous. A minor tension exists between "external AI API"/cloud providers needing their own keys and openWorldHint=false, but the description's own safety claims are consistent with destructiveHint=true.

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?

Purpose, experimental warning, and the alternatives are front-loaded and easy to scan, and the prompt tips with a good/bad example earn their space. However, the Args section restates all five schema parameters nearly verbatim, and the trailing "MAKE DOORS" note about compile_scad is loosely attached to this tool's job.

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 five-parameter, no-output-schema generation tool, the definition covers the full lifecycle (submit → poll → download) and the validation caveat an agent needs before printing. Remaining gaps are minor: no sense of latency or cost per provider, and the special-case behaviour for openscad results ("immediately available") is stated but not tied into the polling guidance an agent would otherwise follow.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: material is a design hint for prompt enrichment rather than a slicing setting and should be left empty when undecided, providers are split into cloud (per-provider key required) versus local keyless openscad, style is ignored by providers other than meshy/gemini, and prompt is capped at 600 chars / ~200 words with a concrete good/bad example. The repeated Args block and duplicated style/provider text keep it from a 5.

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?

Opens with a specific verb + resource + mechanism: "Generate a 3D model from a text prompt via external AI API (Meshy/etc)". It then explicitly separates itself from generate_model_from_image (images), generate_from_template (parametric, local), and generate_and_print (slice+upload), so an agent can classify the request without opening any schema.

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?

Gives an explicit routing rule ("Start here if user has no template/image — just a text description") plus named alternatives for each other case, and even a when-not rule: prefer marketplace community models, use generation only for custom/unique objects. The provider/key guidance and the instruction to leave material empty when undecided add further selection context.

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