Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Run one-way or two-way ANOVA

statistics_anova
Read-onlyIdempotent

One-way and two-way ANOVA with interaction (Type II or III sums of squares), R-squared, Tukey HSD post-hoc comparisons and the Brown-Forsythe (median-centred Levene) test of equal variances. Sums of squares use centred two-pass accumulation and match NIST StRD SiRstv. Price $0.03 USDC. POST /api/v1/statistics/anova. 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": {
      "design": "<design>",
      "rows": "<rows>"
    },
    "name": "statistics_anova"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesrows, array. Required.
designYesdesign, string, one of one_way, two_way. Required.
leveneNolevene, boolean. Required.
ssTypeNossType, string, one of II, III. Required.II
posthocNoposthoc, string, one of tukey, none. Required.none
confidenceNoconfidence, number. Required.

Output Schema

NameRequiredDescriptionDefault
tableNotable. Array.
tukeyNotukey. Array.
leveneNolevene. Object.
sourcesNosources. Array.
rSquaredNorSquared. Number.
droppedRowsNodroppedRows. Number.
limitationsNolimitations. Array.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower, and the description still adds real behavioral context: a fixed price of $0.03 USDC, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without running the analysis. It also discloses the numerical method (centred two-pass accumulation) and a validation benchmark (NIST StRD SiRstv), which builds trust in results. It stops short of describing failure modes such as non-numeric or missing data handling.

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?

The statistical capabilities are front-loaded in a single dense sentence, followed by method provenance, then the commercial/transport details. Every sentence carries information, though the feature list reads as a run-on enumeration rather than being grouped by capability.

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 an output schema present, return values need no explanation, and the description covers pricing, transport, and payment-gating behavior that no structured field conveys. Remaining gaps are minor: no statement about data requirements for rows (numeric response, factor levels) or what happens on invalid designs, but the schema already enforces required fields and enums.

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 the baseline is 3, but the description goes beyond the schema's terse 'ssType, string, one of II, III' by explaining that these are sums-of-squares types used with interaction terms, that posthoc refers to Tukey HSD, and that levene is the Brown-Forsythe median-centred variant. That materially clarifies three of the six parameters. It does not address the rows/design payload structure, but the schema already does.

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?

The opening sentence names the specific verb and resource (one-way and two-way ANOVA with interaction) and enumerates the concrete outputs/tests produced: Type II/III sums of squares, R-squared, Tukey HSD, and Brown-Forsythe. That distinguishes it immediately from siblings such as statistics_t-test and statistics_linear-regression, which cover different statistical procedures.

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 feature list: post-hoc comparisons are offered, so an agent can infer this is for comparing group means across three or more levels. However, the description never states when to prefer ANOVA over statistics_t-test or statistics_nonparametric-tests, nor any prerequisites such as minimum group sizes or balanced designs. The guidance is inferable but not explicit.

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