Skip to main content
Glama

Stat Homogeneity Test

stat_homogeneity_test

Tests equality of variances across groups before independent-samples t-tests or ANOVA, so you can choose Welch alternatives if the assumption fails.

Instructions

Test equality of variances across groups.

When to use: before an independent-samples t-test or a one-way ANOVA. When it fails: use Welch's t-test or Welch's ANOVA, which do not assume equal variances.

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>",
      "group": "<group>"
    },
    "name": "stat_homogeneity_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
dvYes
nameYes
groupYes
methodNolevene (default, robust to non-normality) | bartlett (more powerful, assumes normality).levene

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It adds interpretive value (what a failure implies and which alternative to switch to), but never states that the call is a non-destructive computation, whether it requires loaded data as a precondition, or anything about cost/side effects.

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 short, front-loaded sentences: statement of purpose, then precondition, then failure handling. Zero filler and no repetition of schema content.

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. However, for a 4-parameter tool with three undocumented required parameters, the description should have spent a clause mapping `dv` and `group`; as written, an agent can infer intent but not parameter roles.

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 only 25%: only `method` is documented (in the schema, not the description). The three required parameters `name`, `dv`, and `group` carry no explanation anywhere, and the description does not clarify that dv is the continuous variable and group the factor — a gap that directly risks a wrong invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and statistical object — 'Test equality of variances across groups' — which is unambiguous and distinct from correlation/ANOVA/regression siblings. It does not name a sibling to contrast against (e.g., stat_normality_test or stat_sphericity_test), so differentiation is by domain knowledge rather than explicit routing.

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?

Gives an explicit precondition ('before an independent-samples t-test or a one-way ANOVA') and an explicit failure path ('use Welch's t-test or Welch's ANOVA, which do not assume equal variances'). This is exactly the when-to-use / what-next guidance an agent needs to sequence an analysis.

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