Skip to main content
Glama

Stat Assumption Report

stat_assumption_report

Run all assumption checks implied by a parametric test design in one pass before the main analysis to prevent skipped checks.

Instructions

Run every assumption check implied by a design in one pass.

Use this instead of checking assumptions one at a time, so that none is silently skipped. Report the output whether or not the assumptions pass — a check reported only when it fails is not a check.

When to use: after loading and before the main test, for any parametric test. When NOT to use: for purely non-parametric analyses (normality is irrelevant there), or for descriptive work.

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

Input Schema

NameRequiredDescriptionDefault
dvYesDependent variable.
nameYesSession dataset name.
covarNoCovariate, if the design has one.
withinNoWithin-subjects factor, if any.
betweenNoBetween-subjects factor, if any.
subjectNoSubject identifier (required for within-subjects designs).

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?

With no annotations, the description must carry the full behavioral burden. It usefully discloses the reporting convention ('report the output whether or not the assumptions pass'), which tells the agent that passing checks are returned too, but it never says which checks are run for a given design, whether the tool errors or degrades on missing prerequisites, or that execution is read-only.

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 core action, then cleanly sectioned into 'When to use' and 'When NOT to use'. The epigram about a check that only reports failures is slightly rhetorical, but it earns its place by justifying the always-report behavior.

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?

Output schema exists, so return values need not be explained, and the description covers timing, exclusions, and reporting policy for a moderately complex design-driven tool. It would be complete with a sentence on which checks map to which design elements (e.g. normality for within-subjects, homogeneity for between-subjects).

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

Parameters3/5

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

Schema coverage is 100%, so the parameters (dv, name, covar, within, between, subject) are already documented in the schema; the baseline of 3 applies. The description adds the implicit semantic that the parameter combination defines the design and therefore determines which checks run, but gives no per-parameter detail beyond that.

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 resource: 'Run every assumption check implied by a design in one pass.' The phrase 'instead of checking assumptions one at a time' implicitly contrasts with per-check siblings like stat_normality_test and stat_homogeneity_test, though no sibling is named explicitly, which keeps it just short of a 5.

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?

Explicit when-to-use ('after loading and before the main test, for any parametric test') and explicit when-NOT-to-use ('purely non-parametric analyses', 'descriptive work'). Both boundaries are stated, so the agent does not have to infer the exclusion conditions.

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