Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Test data for normality

statistics_normality-test
Read-onlyIdempotent

Anderson-Darling, Shapiro-Wilk (Royston AS R94) and Lilliefors tests of normality with optional normal probability plot coordinates. Shapiro-Wilk and Anderson-Darling agree with SciPy and statsmodels. Price $0.03 USDC. POST /api/v1/statistics/normality-test. 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": {
      "x": "<x>"
    },
    "name": "statistics_normality-test"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesx, array. Required.
plotNoplot, boolean. Required.
testsNotests, array. Required.

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
plotNoplot. Array.
sourcesNosources. Array.
lillieforsNolilliefors. Object.
droppedRowsNodroppedRows. Number.
limitationsNolimitations. Array.
shapiro_wilkNoshapiro_wilk. Object.
anderson_darlingNoanderson_darling. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the bar is lower, yet the description still adds genuinely useful behavior: a $0.03 USDC price, the POST /api/v1/statistics/normality-test transport, and critically that an unpaid call returns x402 payment terms without running. That payment-failure mode is not derivable from any structured field. It stops short of noting rate limits or input-size constraints.

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?

Four short sentences, front-loaded with the concrete test names, then compatibility evidence, then cost and endpoint. Every sentence carries information, though the endpoint string and price could arguably be tightened without loss.

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 and annotations cover the safety profile, so the description need not explain return values. It covers what the tool computes, the optional plot output, cost and the payment gate. Minor gaps remain around sample-size validity for each test and any cap on the input array length.

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 the baseline is 3. The description adds only marginal meaning, clarifying that the plot option yields normal probability plot coordinates rather than a rendered image, but it does not explain the tests array selection semantics or null handling beyond what the schema already says.

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: normality tests (Anderson-Darling, Shapiro-Wilk Royston AS R94, Lilliefors) with optional normal probability plot coordinates. This is clearly distinguishable from siblings such as statistics_t-test, statistics_anova, or statistics_nonparametric-tests, which serve different inference goals.

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 implied by the purpose rather than stated: an agent can infer it applies when checking a numeric sample for normality. There is no explicit when-to-use versus statistics_nonparametric-tests, no sample-size caveats for Shapiro-Wilk, and no statement of assumptions. The SciPy/statsmodels agreement sentence is a validation claim, not guidance.

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