Skip to main content
Glama

Moldability Screen

moldability_screen
Read-only

Evaluates wall-thickness uniformity and resin shrinkage from wall samples or nominal thickness to flag sink, warp, and cavity-scale issues before molding.

Instructions

Moldability DFx screen (NO solver, NO geometry) — fast analytic gate combining two checks molders reason about first: (1) WALL-THICKNESS QUALITY — is the nominal wall in the resin's recommended moldable band, and is the section uniform enough (uniformity_ratio = t_max/t_min; warn >2, fail >3) to avoid sink/warp; thick-lobe samples (> sink_factor·nominal, k≈1.5) flagged; cooling tied to the thickest wall (t ∝ s²). (2) SHRINKAGE — first-order from the resin CTE: S_linear = alpha·ΔT, S_vol ≈ 3·S_linear, cavity_scale_factor = 1/(1−S_linear); semicrystalline resins (PP/PE/PA/POM/PLA/HDPE/LDPE) flag model_underpredicts and carry a published_shrinkage_pct.

Pass wall_samples (local wall thicknesses, mm) and/or nominal_mm, plus material. Degrades gracefully when the corpus lacks the (issue #106) recommended-wall / mold-shrinkage / crystallinity fields. Low-fidelity gate: escalate_to='molding_fill_submit'.

Returns {thickness:{…}, shrinkage:{…}, material, pass, score, fidelity, band_pct, warnings, escalate_to}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moldability_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
wall_samplesNo

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.6/5.0
Behavior5/5

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

The annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavioral context: analytic-only behavior, threshold formulas, graceful degradation when corpus fields are missing, warning conditions, and escalation behavior. This is consistent with the read-only annotations and gives an agent a clear picture of what the tool does and does not do.

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 with purpose and scope, and the technical formulas and thresholds earn their place for a complex screening tool. It is dense and could be structured more cleanly, but it is not padded with irrelevant text.

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

Completeness5/5

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

For a complex 10-parameter tool with no output schema and limited annotations, the description is unusually complete. It covers purpose, core inputs, behavioral limits, degradation behavior, escalation, and the return object keys.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10%, so the description must carry parameter meaning. It documents the core inputs and relationships well, including wall_samples, nominal_mm, material, warn/fail ratios, sink_factor, and alpha-related shrinkage, but it does not explicitly explain workspace, t_ambient_c, or t_solidify_c.

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 gives a specific verb/resource and scope: an analytic DFx gate for wall-thickness quality and shrinkage, explicitly with no solver and no geometry. It also distinguishes its low-fidelity role by naming molding_fill_submit as the escalation path.

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?

It clearly frames this as a fast early screening gate and says to escalate to molding_fill_submit when low fidelity is insufficient. However, it does not explicitly distinguish when to use this versus similarly named siblings such as moldability_check or molding_screen.

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