Skip to main content
Glama

analyze_generation_feedback

Read-only

Analyze a generated 3D model for printability issues and return specific prompt constraints to fix identified problems before reprinting.

Instructions

Analyze a generated model and get feedback for improvement.

        Returns feedback with specific constraints to add to the
        generation prompt to fix identified issues.

        Args:
            file_path: Path to the generated model file.
            original_prompt: The original generation prompt.
            failure_mode: Optional failure mode if the model was printed
                and failed (e.g. ``"adhesion"``, ``"spaghetti"``).
            max_overhang_angle: Maximum overhang angle in degrees.
            min_wall_thickness: Minimum wall thickness in mm.
            has_bridges: Whether the model has bridge features.
            has_floating_parts: Whether the model has disconnected parts.
            non_manifold: Whether the mesh is non-manifold.
        

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>",
      "original_prompt": "<original_prompt>"
    },
    "name": "analyze_generation_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the generated model file.
has_bridgesNoWhether the model has bridge features. Default: false.
failure_modeNoOptional failure mode if the model was printed and failed (e.g. ``"adhesion"``, ``"spaghetti"``).
non_manifoldNoWhether the mesh is non-manifold. Default: false.
original_promptYesThe original generation prompt.
has_floating_partsNoWhether the model has disconnected parts. Default: false.
max_overhang_angleNoMaximum overhang angle in degrees.
min_wall_thicknessNoMinimum wall thickness in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • addedInput schema / properties / failure_mode / description
      Added value: +"Optional failure mode if the model was printed and failed (e.g. ``\"adhesion\"``, ``\"spaghetti\"``)."
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the generated model file."
    • changedInput schema / properties / has_bridges / description
      Previous value: -"Default: false."New value: +"Whether the model has bridge features. Default: false."
    • changedInput schema / properties / has_floating_parts / description
      Previous value: -"Default: false."New value: +"Whether the model has disconnected parts. Default: false."
    • addedInput schema / properties / max_overhang_angle / description
      Added value: +"Maximum overhang angle in degrees."
    • addedInput schema / properties / min_wall_thickness / description
      Added value: +"Minimum wall thickness in mm."
    • changedInput schema / properties / non_manifold / description
      Previous value: -"Default: false."New value: +"Whether the mesh is non-manifold. Default: false."
    • addedInput schema / properties / original_prompt / description
      Added value: +"The original generation prompt."
  2. Changed9 schema fields changedv1.5.0
    • removedInput schema / properties / failure_mode / default
      Removed value: -null
    • removedInput schema / properties / has_bridges / default
      Removed value: -false
    • addedInput schema / properties / has_bridges / description
      Added value: +"Default: false."
    • removedInput schema / properties / has_floating_parts / default
      Removed value: -false
    • addedInput schema / properties / has_floating_parts / description
      Added value: +"Default: false."
    • removedInput schema / properties / max_overhang_angle / default
      Removed value: -null
    • removedInput schema / properties / min_wall_thickness / default
      Removed value: -null
    • removedInput schema / properties / non_manifold / default
      Removed value: -false
    • addedInput schema / properties / non_manifold / description
      Added value: +"Default: false."
  3. First observedv0.1.0

TDQS

A3.6/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 safety is covered and the description adds real value on top: it explains that the return payload is feedback plus concrete constraints intended to be re-injected into a generation prompt, which is the key behavioral fact. It still omits things like whether the file is read from disk, how failures are reported, or response shape details.

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 earn their place, but the Args section duplicates the input schema line-for-line and adds no new information, which inflates the description without adding value.

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 an 8-parameter read-only analysis tool with no output schema, the description covers the input contract and gives a usable sketch of what comes back (feedback plus prompt constraints). It could go further by describing the structure of the returned feedback or how the optional geometric flags (has_bridges, non_manifold, etc.) change the analysis, but nothing essential to calling it correctly is missing.

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% and the Args block in the description is essentially a verbatim restatement of the schema descriptions, including the failure_mode examples. No additional meaning is added, such as units interpretation, valid ranges for max_overhang_angle, or how original_prompt influences the analysis. Baseline 3 applies.

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 states a specific verb and resource ('Analyze a generated model') and clarifies the deliverable ('feedback with specific constraints to add to the generation prompt'). That distinguishes it reasonably from generic mesh analyzers, though it never names a sibling such as analyze_printability or improve_generation_prompt to sharpen the boundary.

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?

Usage is only implied: the failure_mode parameter hints that the tool is relevant after a model has been printed and failed. There is no explicit statement of when to prefer this over the many other analysis/feedback siblings, and no when-not guidance or prerequisites (e.g. that file_path must be a model generated by this service).

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