Skip to main content
Glama

Stat Pairwise Tukey

stat_pairwise_tukey

Run Tukey HSD or Games-Howell post-hoc tests after a one-way ANOVA to compare group means, choosing Games-Howell when variances or group sizes differ.

Instructions

Tukey HSD or Games-Howell post-hoc tests after a one-way ANOVA.

WHEN TO USE

  • Tukey HSD: equal variances and roughly equal group sizes (the standard default).

  • Games-Howell (method="gameshowell"): unequal variances or unequal group sizes — i.e. whenever Levene's test is significant.

WHEN NOT TO USE: for within-subjects designs — use stat_pairwise_tests with the subject argument instead.

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_pairwise_tukey"
  }
}

Input Schema

NameRequiredDescriptionDefault
dvYes
nameYes
methodNotukey
betweenYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 discloses the key assumption-driven branch (variance equality dictates method), which is valuable, but says nothing about whether the tool refits its own ANOVA from dv/between, how missing data or unbalanced cells are handled, or that the default method is tukey — the caller must infer this from raw columns despite the 'after a one-way ANOVA' framing.

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?

Well front-loaded: the one-line purpose precedes labeled WHEN TO USE / WHEN NOT TO USE blocks, and each line carries decision-relevant content. Slightly heavy for a four-parameter tool, but nothing is redundant.

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-value explanation is not required, and method selection is well covered. However, with no annotations and zero schema coverage, the definition leaves the required column arguments and the model-vs-raw-data expectation unexplained — gaps an agent would hit at invocation time.

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% across 4 parameters, so the description must compensate and largely does not. It only clarifies `method` (default tukey, alternative "gameshowell"); `name`, `dv`, and `between` are never explained, leaving the three required parameters undocumented in both schema and prose.

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?

Opens with a specific verb and resource: Tukey HSD / Games-Howell post-hoc tests following a one-way ANOVA. It explicitly names the sibling it is not (stat_pairwise_tests for within-subjects designs), so an agent can route without opening another 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?

Gives explicit when-to-use rules per method (Tukey HSD for equal variances/equal n; Games-Howell when Levene's test is significant), plus an explicit when-not-to-use case with the named alternative. Selection criteria are fully specified rather than implied.

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