Skip to main content
Glama

Molding Screen

molding_screen
Read-only

Estimate injection-molding cooling time from wall thickness, temperatures, and thermal diffusivity, then check spiral-flow fill length against a chart correlation (±30%) using material defaults.

Instructions

Injection-molding screen (NO solver): one-term cooling time (exact given α, t_cool = s²/(π²α)·ln(8·(T_melt−T_mold)/(π²·(T_eject−T_mold))) — the t ∝ s² design lever) + the spiral-flow fill check (fill_ok when flow_length ≤ (L/t-limit)·wall — chart correlation, ±30 %). material picks per-polymer defaults (ABS | PP | PC | PA66 | POM | HDPE | PS), each individually overridable; with all temps + alpha_mm2_s explicit no material is needed. A cooling-only call returns fidelity='exact'; adding flow_length_mm makes the headline answer fidelity='correlation', band_pct=30 (cooling stays exact). When a flow_length_mm is given the headline check is a chart correlation, so escalate_to='molding_fill_submit' (the openInjMoldSim VOF fill solve, #105); a cooling-only call needs no solver and returns escalate_to=None.

Returns {material, wall_thickness_mm, t_melt_c, t_mold_c, t_eject_c, alpha_mm2_s, cooling_time_s, flow_length_mm, flow_ratio, flow_ratio_limit, fill_ok, fidelity, band_pct, valid_range_ok, warnings, escalate_to}.

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": {
      "wall_thickness_mm": "<wall_thickness_mm>"
    },
    "name": "molding_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNo
t_melt_cNo
t_mold_cNo
t_eject_cNo
workspaceNoRun this call in this named workspace
alpha_mm2_sNo
flow_length_mmNo
flow_ratio_limitNo
wall_thickness_mmYes

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.3/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint; the description goes further by disclosing that cooling is exact while the flow check is a ±30% chart correlation, that band_pct=30 applies only to the correlation path, and that valid_range_ok and warnings are returned. It does not state what valid_range_ok checks or what conditions trigger warnings.

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 opening clause front-loads the essential framing (what it is, that it needs no solver), and every subsequent sentence carries real information about modes, fidelity, or escalation. It is dense and formula-heavy, and the trailing field enumeration is long, but with no output schema that listing 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 9-parameter physics screen with no output schema, the description supplies the governing formula, the mode switch, fidelity semantics, the escalation target, and the full return shape — enough for an agent to call and interpret it correctly. The undocumented `workspace` parameter is the main remaining gap.

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 11%, so the description must compensate — and it largely does: it enumerates the material options (ABS | PP | PC | PA66 | POM | HDPE | PS), explains that per-polymer defaults are individually overridable, ties s in the formula to wall_thickness_mm, and clarifies that flow_length_mm switches the mode. The `workspace` parameter is never mentioned and flow_ratio_limit is only obliquely referenced as 'L/t-limit'.

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+resource — 'Injection-molding screen (NO solver)' — and immediately names the two computations it performs (one-term cooling time plus spiral-flow fill check). The 'NO solver' qualifier plus the escalate_to='molding_fill_submit' reference cleanly separates it from molding_fill_submit, molding_warpage_submit, and the moldability_* siblings.

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?

Gives a clear conditional usage rule: a cooling-only call needs no solver and returns escalate_to=None, while supplying flow_length_mm makes the headline answer a correlation and warrants escalation to molding_fill_submit. It also states the material-optional path (all temps + alpha_mm2_s explicit). It does not, however, say when to choose this over moldability_screen or moldability_check, which are the closest conceptual siblings.

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