Skip to main content
Glama

Future Micro Mold Lab

Gage R&R (crossed, ANOVA method)

gage_rr
Read-onlyIdempotent

Rate a measurement system from a crossed study: every operator measures every part, the same number of times. Two-way ANOVA per the AIAG Measurement Systems Analysis manual (4th ed.), matching Minitab's crossed gage R&R defaults: the operator × part interaction is pooled into repeatability when not significant (α = 0.05). Reports %GRR of study variation and, when a tolerance is given, of the tolerance, the repeatability / reproducibility split, the number of distinct categories, and the AIAG band (under 10% acceptable, 10–30% conditional, over 30% unacceptable). The standard study is 10 parts, 3 operators, 2–3 trials. Run it before trusting a Cpk.

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

Input Schema

NameRequiredDescriptionDefault
contextNo
operatorsNo
toleranceNoTolerance width (upper limit minus lower limit), same units as the readings. Enables %GRR of tolerance, which is what a Cpk study needs.
study_codeNoA study as the Lab card encodes it; use instead of the measurements (operators, tolerance)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish this as a safe, idempotent, non-destructive read, and the description adds real behavioral substance on top: the interaction-pooling rule into repeatability at α = 0.05, the AIAG/Minitab default it matches, and the exact set of reported statistics including the 10/30% acceptability bands. That is enough for an agent to predict both the computation and the shape of the answer.

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 method, then the statistical behavior, then the reported outputs and the practical sequencing advice. Dense but essentially every clause carries information; the parenthetical band definitions and edition citation are justified for a regulated-method tool.

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?

With no output schema, the description properly carries the return-value burden by enumerating %GRR of variation and tolerance, the repeatability/reproducibility split, distinct categories, and the AIAG band. The remaining gap is the unexplained context object, which the description never mentions despite it being a nested parameter.

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?

The description implies the tolerance parameter ("when a tolerance is given") and characterizes the intended study design (10 parts, 3 operators, 2–3 trials), which adds meaning beyond the schema's min/max bounds. However, it says nothing about the study_code alternative or the context object (material, meltTempC, moldTempC), which is the undocumented half of the 50% schema coverage.

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 ("rate a measurement system from a crossed study") and immediately pins down the method (two-way ANOVA, AIAG MSA 4th ed., Minitab-compatible defaults). It also positions itself against a sibling by telling the agent to run it before trusting a Cpk, so the agent can distinguish it from process_capability without opening either schema.

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 clear usage context — a crossed design where every operator measures every part the same number of times, plus the sequencing rule "run it before trusting a Cpk." It stops short of explicit exclusions (e.g., what to do for nested or non-crossed studies) and names no alternative tool for those cases.

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