Skip to main content
Glama

Optics Moldability Check

optics_moldability_check
Read-only

Check a part's moldability along one pull axis: detect undercut faces, draft violations and thin walls, then return a scored pass/fail result with wall-thickness statistics.

Instructions

Moldability screen for a part against a single pull axis — geometric, no solver. Resolves the model handle's solid, then per face computes the draft relative to pull_axis from the outward normal (draft_deg = 90 − angle(normal, pull); 0 = a wall parallel to the pull that needs draft) and ray-casts the face centroid along ±pull: a face the straight pull frees in neither direction is a re-entrant UNDERCUT (reported with negative draft). Inward chords give a wall- thickness distribution. Scored through the same DfM machinery as dfm_check.

pull_axis: '+z'/'-x'/… or an [x,y,z] vector. process ('injection'|'cnc'| 'sheet'|'fdm') sets the default min wall; override with min_wall_mm.

Returns {process, pull_axis, n_faces, undercut_faces, draft_violations, min_wall_violations, wall_thickness_stats:{min_mm,mean_mm,max_mm,n}, score, pass}.

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": {
      "model": "<model>"
    },
    "name": "optics_moldability_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
processNoinjection
pull_axisNo+z
workspaceNoRun this call in this named workspace
min_wall_mmNo
min_draft_degNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds substantial behavioral detail beyond that: geometric-only execution, per-face draft computation, ray-casting along ±pull, undercut detection, wall-thickness distribution, and the returned fields. This is exactly the kind of algorithmic and output context an agent needs for a complex check.

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 front-loaded: the first sentence states what the tool does, then it adds algorithmic detail and return fields. It is long and includes some implementation detail, but for a geometric check with no output schema most of it earns 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 complex tool with no output schema, the description does a good job explaining the computation and listing return fields. The remaining gaps are the missing explanation of min_draft_deg and the lack of explicit sibling differentiation.

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 only 17%, so the description must carry parameter meaning. It does well on pull_axis formats, process values, and the min_wall_mm override, but it does not explain min_draft_deg, and the required model parameter is left implicit. Partial compensation, not full.

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 first sentence gives a specific verb and resource: a moldability screen for a part against a single pull axis, geometric with no solver. That is clear enough to distinguish it from most non-DFM tools, but the description never explains how it differs from close siblings like moldability_check, moldability_screen, or molding_screen.

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 implied by the purpose statement, but there is no explicit guidance on when to choose this tool over the many nearby moldability/DFM alternatives. It also gives no when-not conditions, so the agent must infer selection from the name and the mention of dfm_check machinery.

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