Skip to main content
Glama

preview_generated_model

Read-only

Render a generated 3D model to multi-angle PNG previews for visual inspection; check floating geometry, thin walls, and print risks before slicing or printing.

Instructions

Specialized post-generation verification renderer. For general-purpose model viewing, use visualize_model instead. This tool adds generation-specific checks (floating geometry, thin walls) on top of the standard multi-angle renders.

        Render a 3D model to multi-angle PNG previews for visual inspection.

        **REQUIRED** before printing any generated model.  You MUST call this
        tool after generating a model and BEFORE printing.  View ALL rendered
        angles to check for:
        - Missing or simplified features (e.g., plain box instead of pattern)
        - Incorrect proportions or dimensions
        - Floating/disconnected geometry
        - Thin walls that won't print
        - Overhangs that need supports
        - Non-manifold artifacts
        - Bottom surface not flat (check bottom view for bed adhesion)
        - Elephant's foot risk on first layer

        **Required workflow:**
        1. Call ``generate_model`` or ``generate_model_from_image``
        2. **MUST** call ``preview_generated_model`` — view ALL angles
        3. If the model doesn't match the request, regenerate with refined prompt
        4. Call ``validate_generated_mesh`` for structural checks
        5. Only then proceed to print

        Args:
            file_path: Path to an STL or 3MF file to render.  A colored
                3MF is rendered with its per-face colors.
        

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": {
      "file_path": "<file_path>"
    },
    "name": "preview_generated_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to an STL or 3MF file to render. A colored 3MF is rendered with its per-face colors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to an STL or 3MF file to render.  A colored 3MF is rendered with its per-face colors."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds value by disclosing the output form (multi-angle PNGs for visual inspection), that colored 3MF renders per-face colors, and what the extra generation-specific checks look for. It stops short of stating angle count or how many images are returned, 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.

Conciseness3/5

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

The opening two sentences are well front-loaded and the workflow list is useful, but the eleven-item defect checklist plus a five-step workflow plus an Args block that merely duplicates the schema make it longer than necessary. Trimming the Args duplication and consolidating the checklist would sharpen it without losing information.

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 single-parameter read-only renderer with no output schema, the description covers purpose, alternative, pipeline position, output medium, and what to look for. The only real gap is quantitative detail about the render set (number of angles, resolution), which is minor given the annotations already establish the safe read profile.

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% and the single parameter's schema description is repeated verbatim in the Args block (STL/3MF path, colored 3MF per-face colors). No additional meaning, format examples, or constraints are added beyond the structured field, so the baseline of 3 applies.

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 states a specific verb and resource ("Render a 3D model to multi-angle PNG previews") and immediately differentiates itself from the closest sibling by name: "For general-purpose model viewing, use visualize_model instead." It further narrows its niche as a "post-generation verification renderer" that layers generation-specific checks (floating geometry, thin walls) on standard renders.

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?

Explicitly names when to use this tool versus the alternative (visualize_model), declares itself REQUIRED after generation and before printing, and supplies an ordered five-step workflow placing it between generate_model and validate_generated_mesh. An agent knows exactly where this call belongs in the pipeline.

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