Skip to main content
Glama

Stat Mixed Anova

stat_mixed_anova

Run a mixed-design ANOVA to test one between-subjects factor and one within-subjects factor, including their interaction, for group × time or repeated-measures designs.

Instructions

Mixed-design ANOVA — one between-subjects factor crossed with one within-subjects factor.

WHEN TO USE: e.g. two groups measured at three time points; group × time designs.

Read the interaction first. A significant interaction means the effect of one factor depends on the level of the other, and the main effects must not be interpreted in isolation.

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>",
      "within": "<within>",
      "subject": "<subject>",
      "between": "<between>"
    },
    "name": "stat_mixed_anova"
  }
}

Input Schema

NameRequiredDescriptionDefault
dvYes
nameYes
withinYes
betweenYes
effsizeNonp2
subjectYes
correctionNoauto

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 genuine analytical guidance ('read the interaction first ... main effects must not be interpreted in isolation'), but says nothing about assumptions checked, what the output contains, or whether it reports sphericity corrections — leaving real gaps for a no-annotation tool. The presence of an output schema offsets the return-value omission somewhat.

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?

Front-loaded with the method definition, then a labeled usage block, then one interpretive caveat. Every sentence contributes; the only weakness is that no space was spent on parameter meaning where it was most needed.

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?

The core statistical concept and the interaction-reading caveat are well covered, and an output schema exists so return values needn't be explained. However, for a 7-parameter tool with zero schema coverage and no annotations, the complete absence of parameter explanations leaves an agent guessing at the most error-prone part of the call.

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 7 terse parameters (dv, subject, effsize, correction, etc.). The description only implicitly illuminates `within` and `between` via the 'crossed' phrasing; the outcome variable, subject identifier, effect-size choice, and correction behavior are entirely undocumented in both schema and description.

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 method (mixed-design ANOVA) and precisely what design it handles: 'one between-subjects factor crossed with one within-subjects factor.' This distinguishes it conceptually from a plain between-subjects ANOVA or a repeated-measures ANOVA, though it never names those siblings explicitly.

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

Usage Guidelines4/5

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

The 'WHEN TO USE' block gives concrete design examples ('two groups measured at three time points; group × time designs'), which is exactly the context an agent needs to route to this tool over stat_anova or stat_rm_anova. It stops short of stating exclusions or naming the alternatives to use instead.

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