Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Compute control chart limits and violations

statistics_control-chart
Read-onlyIdempotent

Control limits and Western Electric or Nelson rule violations for I-MR, X-bar R, X-bar S, p, np, c and u charts from caller-supplied measurements or counts, with optional fixed Phase II limits. Price $0.04 USDC. POST /api/v1/statistics/control-chart. 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": {
      "chart": "<chart>"
    },
    "name": "statistics_control-chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNosize, integer, from 1 to 9007199254740991. Optional.
chartYeschart, string, one of imr, xbar_r, xbar_s, p, np, c. Required.
phaseNophase, string, one of I, II. Required.I
rulesNorules, array. Required.
sizesNosizes, array. Optional.
countsNocounts, array. Optional.
limitsNolimits, object. Optional.
valuesNovalues, array. Optional.
subgroupsNosubgroups, array. Optional.

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
lclNolcl. Number.
uclNoucl. Number.
chartNochart. String.
phaseNophase. String.
centerNocenter. Number.
pointsNopoints. Array.
sourcesNosources. Array.
secondaryNosecondary. Object.
limitationsNolimitations. Array.
sigmaWithinNosigmaWithin. Number.
subgroupSizeNosubgroupSize. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds real operational context: a fixed price of $0.04 USDC and the concrete failure behavior that an unpaid call returns x402 payment terms without running. That payment-gating detail is exactly the kind of thing an agent cannot get from annotations or schema; only the return payload shape is left implicit (and an output schema exists).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with zero filler: capability and chart coverage first, then cost/endpoint, then the unpaid-call failure mode. Front-loading the capability before the payment caveat lets an agent decide relevance before it has to care about billing.

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?

Output shape needn't be described because an output schema exists, and the payment path is covered. The remaining gap is that it never states which input array pairs with which chart type (values for I-MR, subgroups for X-bar, counts for p/np/c/u, sizes for p/u) — a consequential omission for a 9-parameter tool with a nested limits object.

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 earns above it by mapping inputs to parameter families ('measurements' vs 'counts') and clarifying that 'limits' are fixed Phase II limits rather than computed ones. It also distinguishes the two rule vocabularies (Western Electric vs Nelson), which explains the we*/n* enum prefixes in a way the schema does not.

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?

Specific verb ('Compute') plus resource ('control limits and Western Electric or Nelson rule violations') and an explicit enumeration of supported chart types (I-MR, X-bar R, X-bar S, p, np, c, u). It clearly separates this from the regression/ANOVA/normality siblings by naming a concrete statistical artifact and its inputs (measurements or counts, fixed Phase II limits).

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 context is implied by naming the input forms ('caller-supplied measurements or counts', 'optional fixed Phase II limits'), so an agent can infer when the tool applies. However, nothing states when to prefer this over process-capability or time-series-decompose, and no prerequisites or exclusions are given.

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