Skip to main content
Glama

Future Micro Mold Lab

Cosmetic process-window study

cosmetic_window
Read-onlyIdempotent

Map which combinations of two process parameters produce a cosmetically acceptable part, and how much room surrounds the centre. Sweep wider than you expect the window to be: a passing point on the edge of the range tested means the window was never closed on that side. Axes and their units: hold_pressure (psi), melt_temp (°C), mold_temp (°C), injection_velocity (in/s), hold_time (s), cooling_time (s). Defects: short, flash, sink, burn, splay, weld-line, drag, warp.

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

Input Schema

NameRequiredDescriptionDefault
xAxisNoHorizontal parameter. Units by axis: hold_pressure (psi), melt_temp (°C), mold_temp (°C), injection_velocity (in/s), hold_time (s), cooling_time (s).
yAxisNoVertical parameter. Units by axis: hold_pressure (psi), melt_temp (°C), mold_temp (°C), injection_velocity (in/s), hold_time (s), cooling_time (s).
pointsNo
contextNo
study_codeNoA study as the Lab card encodes it; use instead of the measurements (xAxis, yAxis, points)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds genuine interpretive context beyond that: edge passes imply an unclosed window, which changes how an agent should read the result and how wide to sample. It stops short of describing what the response contains.

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 purpose leads, the sweep caveat follows, and the axis/defect lists are compact. The axis-unit and defect enumerations largely duplicate the schema, so a sentence or two is less load-bearing than the rest.

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?

No output schema exists, so the description should say what the study yields, and it does: an acceptable window plus the room around its centre, with a warning about open edges. The remaining omissions, notably the study_code input path and the sampling limits, are covered by the schema's own descriptions.

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 60% and the description restates the axis units and defect names that the schema already enumerates for xAxis, yAxis and the defect field, so it adds little for those. It says nothing about the points array limits, the context object, or the study_code alternative input path, so uncovered parameters stay unexplained.

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 names a specific verb and resource: mapping which combinations of two process parameters yield a cosmetically acceptable part, plus the surrounding margin. That is distinctly different from the quantitative siblings (process_capability, cavity_balance, gate_seal) and an agent can tell what it produces without opening the schema.

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?

It gives a methodological rule for the data ('sweep wider than you expect the window to be') and warns that a pass on the range edge means the window is still open, which is useful guidance. However, it never says when to pick this study over a sibling such as process_capability or plan_process_development, so the routing decision is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources