Skip to main content
Glama

Moldability Check

moldability_check
Read-only

Evaluates whether a 3D model can be molded by sampling local wall thickness and estimating resin CTE shrinkage, returning pass/fail warnings and a low-fidelity gate to escalate fill simulation.

Instructions

Geometry-aware moldability DFx screen — resolves the model handle's solid, samples local wall thickness per face via inward chords (the same machinery as optics_moldability_check), then grades it through the pure-Python moldability screen: WALL-THICKNESS QUALITY (recommended-band range / uniformity / sink risk, cooling tied to the thickest wall) + the CTE SHRINKAGE estimate for the resin. Low-fidelity gate — escalate_to= 'molding_fill_submit'.

material drives the recommended-wall band, the CTE shrinkage, and cooling (degrades gracefully when the corpus lacks the issue #106 fields). nominal_mm anchors the range check (else the sampled-wall mean). The same shrinkage/thickness overrides as moldability_screen apply.

Returns the moldability_screen verdict {thickness:{…}, shrinkage:{…}, pass, score, fidelity, band_pct, warnings, escalate_to} plus {n_faces, n_wall_samples}.

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

Input Schema

NameRequiredDescriptionDefault
modelYes
materialNo
workspaceNoRun this call in this named workspace
fail_ratioNo
nominal_mmNo
warn_ratioNo
alpha_per_kNo
sink_factorNo
t_ambient_cNo
t_solidify_cNo

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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds substantive context beyond them: it discloses the internal sampling step, that it is a low-fidelity gate, that material-driven behavior 'degrades gracefully when the corpus lacks the issue #106 fields', and the exact shape of the returned verdict. It says nothing about cost or runtime of the chord sampling, which is the main residual gap.

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?

Front-loaded with the core action and the escalation target, with per-parameter notes and the return shape clearly grouped in separate sentences. It is dense but nearly every clause carries information; the parenthetical '(the same machinery as optics_moldability_check)' is the one bit of slack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters, 10% schema coverage and no output schema, the description does well on the return value (it enumerates the verdict keys plus n_faces/n_wall_samples) and on escalation, but leaves the majority of tuning parameters defined only by cross-reference to moldability_screen. For a tool with this many knobs, an agent still cannot tell what changing fail_ratio or sink_factor actually does.

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 10% (just `workspace`), so the description has to carry the load and it only partly does: it explains `material` (drives wall band, CTE shrinkage, cooling) and `nominal_mm` (anchors range check, else sampled-wall mean). The six numeric knobs (fail_ratio, warn_ratio, sink_factor, alpha_per_k, t_ambient_c, t_solidify_c) are covered only by the hand-wave 'the same shrinkage/thickness overrides as moldability_screen apply', which forces the agent to consult another tool's docs.

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?

States a specific verb and resource ('Geometry-aware moldability DFx screen') and immediately names the mechanism: resolve the model handle's solid, sample wall thickness per face via inward chords, grade through the pure-Python moldability screen. It also differentiates itself from siblings by naming optics_moldability_check (same machinery), moldability_screen (verdict source) and molding_fill_submit (escalation target).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Low-fidelity gate — escalate_to='molding_fill_submit'' gives an explicit escalation path once the result comes back, which is real routing guidance. It stops short of stating when to pick this over moldability_screen (pure screen, no geometry) or optics_moldability_check, so the selection rule must be inferred from the 'geometry-aware' framing.

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