Skip to main content
Glama

infer_print_settings

Read-only

Analyze an STL mesh for structural risks and recommend material-specific slicer settings—perimeters, infill, supports, brim, and layer height—to improve print success.

Instructions

Infer optimal slicer settings from structural analysis.

        Bridges the gap between **design analysis** and **print success**.
        Analyzes the mesh for structural risks, then recommends concrete
        slicer parameters (perimeters, infill, supports, brim, layer height)
        tuned to compensate for the design's weaknesses.

        **Examples of what it catches:**

        - Thin neck detected → increase perimeters to 4+
        - Cantilever overhangs → enable tree supports
        - High center of gravity → add brim for bed adhesion
        - Stress concentrations → switch to gyroid infill at 50%+
        - Sharp corners → fine layer height for detail

        Material-specific: defaults vary by PLA/PETG/ABS/Nylon/TPU/ASA/PC.

        :param file_path: Path to the STL file.
        :param material: Filament type (PLA, PETG, ABS, Nylon, TPU, ASA, PC).
        :returns: Dict with perimeters, infill, supports, brim, layer height,
                  orientation, special notes, and confidence level.
        

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": "infer_print_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoFilament type (PLA, PETG, ABS, Nylon, TPU, ASA, PC). Default: "PLA".
file_pathYesPath to the STL file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the STL file."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Filament type (PLA, PETG, ABS, Nylon, TPU, ASA, PC). Default: \"PLA\"."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / material / default
      Removed value: -"PLA"
    • addedInput schema / properties / material / description
      Added value: +"Default: \"PLA\"."
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 without the description. The description adds real value beyond that: it discloses that material choice changes defaults across PLA/PETG/ABS/Nylon/TPU/ASA/PC and that the result carries a confidence level. It still omits things that matter operationally, such as whether analysis is expensive/slow on large meshes, what happens on a malformed or non-manifold STL, and what a low confidence value implies.

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 purpose sentence is front-loaded and the 'what it catches' bullets are genuinely informative. However, the 'Bridges the gap between design analysis and print success' line is filler, and the trailing :param/:returns Sphinx block duplicates the input schema verbatim; a good chunk of the text does not earn its place.

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 two-parameter read-only analysis tool with no output schema, the description is close to sufficient: it explains the analytical basis, lists the specific slicer fields returned (perimeters, infill, supports, brim, layer height, orientation, notes, confidence), and notes material-dependence. Only the failure-mode and cost/latency behavior are 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%, with both file_path and material already documented and material's enumerated values and PLA default stated in the schema. The description's :param lines merely restate those definitions and add no format, path-resolution, or case-sensitivity detail, so the baseline 3 is appropriate.

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 opening line gives a specific verb+resource ('Infer optimal slicer settings from structural analysis') and the body makes concrete that it analyzes a mesh and emits slicer parameters. It does not name or distinguish itself from close siblings such as predict_print_settings, recommend_settings, get_optimal_settings, estimate_supports, or recommend_adhesion_settings, so an agent must guess which one to pick.

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: you need an STL and want concrete slicer values. There is no explicit 'use this when...' statement, no prerequisites (does the file need to exist locally? does it need prior analysis?), and no routing to or away from the similarly-purposed sibling tools.

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