Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Calculate process capability indices

statistics_process-capability
Read-onlyIdempotent

Cp, Cpk, Pp, Ppk, Cpm and expected parts per million out of specification from individual values or subgroups, with R-bar, S-bar or pooled within-subgroup sigma, an optional Box-Cox transform and a Bissell interval for Cpk. Price $0.04 USDC. POST /api/v1/statistics/process-capability. An unpaid call returns the x402 payment terms and does not run.

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": "statistics_process-capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
lslNolsl, number. Optional.
uslNousl, number. Optional.
targetNotarget, number. Optional.
valuesNovalues, array. Optional.
subgroupsNosubgroups, array. Optional.
transformNotransform, string, one of none, box_cox. Required.none
withinMethodNowithinMethod, string, one of rbar, sbar, pooled. Required.rbar

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
CpNoCp. Number.
PpNoPp. Number.
CpkNoCpk. Number.
CplNoCpl. Number.
CpmNoCpm. Number.
CpuNoCpu. Number.
PpkNoPpk. Number.
PplNoPpl. Number.
PpuNoPpu. Number.
meanNomean. Number.
cpkCiNocpkCi. Array.
lambdaNolambda. Null.
sourcesNosources. Array.
transformNotransform. String.
droppedRowsNodroppedRows. Number.
limitationsNolimitations. Array.
ppmObservedNoppmObserved. Number.
sigmaWithinNosigmaWithin. Number.
sigmaOverallNosigmaOverall. Number.
withinMethodNowithinMethod. String.
ppmExpectedWithinNoppmExpectedWithin. Number.
ppmExpectedOverallNoppmExpectedOverall. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious operational context: a $0.04 USDC charge, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without running the computation. That payment-failure behavior is exactly the kind of detail that prevents a wasted invocation; only rate limits or response timing are absent.

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 returned indices, then method mechanics, then the payment/endpoint logistics — a sensible order with little waste. The single dense opening clause packs many terms, but each sentence carries distinct information.

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 need not be described, and the description covers pricing, transport (POST path) and statistical options. It is slightly thin on prerequisites — notably that capability indices require lsl/usl and that at least one of values or subgroups must be supplied, despite all parameters being formally optional.

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 coverage is 100%, so baseline is 3, but the description goes further by expanding the cryptic enum values ('R-bar, S-bar or pooled within-subgroup sigma' for withinMethod, 'optional Box-Cox transform' for transform) and by framing values vs subgroups as alternative data sources. It does not explain how lsl/usl/target interact with each index, so it stops short of 5.

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?

Names the exact statistics produced (Cp, Cpk, Pp, Ppk, Cpm, expected PPM) and the inputs they derive from (individual values or subgroups), so an agent knows precisely what this computes. The resource is unmistakably distinct from siblings such as statistics_control-chart or statistics_normality-test.

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?

Usage is only implied: 'from individual values or subgroups' hints at the values-vs-subgroups choice, and the sigma-method mention hints at withinMethod selection. There is no explicit when-to-use/when-not guidance or routing to alternative tools, leaving the agent to infer the selection logic.

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