Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Run a crossed gage R&R study

statistics_gage-rr
Read-onlyIdempotent

Crossed gage repeatability and reproducibility by the ANOVA method: variance components, percent contribution, percent study variation, percent tolerance and number of distinct categories for a balanced parts by operators by replicates study. Price $0.05 USDC. POST /api/v1/statistics/gage-rr. An unpaid call returns the x402 payment terms and does not run.

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": {
      "measurements": "<measurements>"
    },
    "name": "statistics_gage-rr"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranceNotolerance, number. Optional.
measurementsYesmeasurements, array. Required.
studyVarMultiplierNostudyVarMultiplier, value. Required.
removeInteractionAboveNoremoveInteractionAbove, number, from 0 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
ndcNondc. Number.
anovaNoanova. Array.
partsNoparts. Number.
tableNotable. Array.
sourcesNosources. Array.
operatorsNooperators. Number.
componentsNocomponents. Object.
replicatesNoreplicates. Number.
limitationsNolimitations. Array.
pctToleranceNopctTolerance. Number.
pctStudyVarGrrNopctStudyVarGrr. Number.
interactionPooledNointeractionPooled. Boolean.
pctContributionGrrNopctContributionGrr. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive and open-world, so the safety profile is covered. The description adds material context annotations cannot: a $0.05 USDC charge, the exact POST endpoint, and that an unpaid call returns x402 payment terms without running the study — plus the balanced-design requirement, which is a real behavioral precondition.

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 method and output set, then payment and endpoint facts in short sentences. The output-metric enumeration is somewhat dense but each clause maps to something the caller needs; no filler sentences.

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?

An output schema exists, so return values needn't be re-explained, yet the description still summarizes the key statistics. Combined with the pricing/auth behavior and the balanced-design precondition, an agent has enough to decide and invoke correctly; only the absence of alternative-tool routing keeps it short of full completeness.

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 100%, so parameter documentation is already handled. The description contributes the notion that measurements are balanced across parts, operators and replicates, which gives structure to the array, but adds nothing about tolerance, studyVarMultiplier, or removeInteractionAbove beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Crossed gage repeatability and reproducibility by the ANOVA method') and enumerates the outputs (variance components, %GRR, ndc). It is unambiguous what the tool computes, though it does not name or contrast a sibling tool.

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?

Implicit guidance only: the name and 'balanced parts by operators by replicates' framing indicate a measurement-systems analysis on a balanced design study. There is no explicit statement of when to use this rather than statistics_anova or statistics_process_capability, nor of what makes a study unsuitable (e.g., unbalanced data).

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