Skip to main content
Glama

Stat Welch Anova

stat_welch_anova

Compare three or more group means when variances are unequal or sample sizes differ, using Welch’s ANOVA to test for significant differences without the equal-variance assumption.

Instructions

Welch's ANOVA — three or more groups without the equal-variance assumption.

WHEN TO USE: Levene's test is significant, or group sizes and variances differ. WHEN NOT TO USE: when variances are equal — the standard ANOVA is more powerful.

Note: Welch's ANOVA does not yield the usual η²; report ω² or use pairwise effect sizes with a correction.

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": {
      "name": "<name>",
      "dv": "<dv>",
      "between": "<between>"
    },
    "name": "stat_welch_anova"
  }
}

Input Schema

NameRequiredDescriptionDefault
dvYes
nameYes
betweenYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a real behavioral quirk: no usual eta-squared, so omega-squared or corrected pairwise effect sizes should be reported. That is valuable non-obvious context, but it says nothing about normality assumptions, minimum group counts, or failure behavior for a statistical procedure.

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?

Front-loaded one-line definition, then labeled WHEN TO USE / WHEN NOT TO USE blocks, then a short caveat note. Every sentence earns its place and there is no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and the usage guidance is solid. However, for a three-parameter tool with zero schema documentation, the complete absence of parameter meaning leaves a material gap an agent must guess around.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three required parameters (name, dv, between), so the description must compensate — but it never mentions any parameter. 'dv' and 'between' presumably mean dependent variable and grouping factor, and 'name' is genuinely opaque, yet the description leaves all of this to inference.

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 description names the specific test (Welch's ANOVA) and its defining scope: three or more groups without the equal-variance assumption. It explicitly contrasts with 'the standard ANOVA' (sibling stat_anova), so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit WHEN TO USE (Levene's test significant, unequal group sizes/variances) and WHEN NOT TO USE (equal variances, where standard ANOVA is more powerful) conditions, naming the alternative. This is the full when/when-not/alternative triad.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.