Skip to main content
Glama

Stat Equivalence Test

stat_equivalence_test

Test whether two groups are statistically equivalent by specifying a justified equivalence bound, not just a non-significant difference.

Instructions

TOST equivalence test — for demonstrating that two groups are equivalent.

WHEN TO USE: the research claim is that there is no meaningful difference (e.g. a new measure matches an established one).

WHEN NOT TO USE: as a post-hoc rescue of a non-significant t-test. TOST answers a different question and needs its bound specified in advance.

A non-significant difference is not evidence of equivalence — absence of evidence is not evidence of absence. The bound must be justified on substantive grounds (the largest difference that would still be negligible), ideally before data collection.

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

Input Schema

NameRequiredDescriptionDefault
dvYes
nameYes
boundYes
groupYes
pairedNo
subjectNo

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 present, the description carries the full burden and does disclose important behavioral constraints: the bound must be pre-specified and substantively justified, and the result is not interchangeable with a non-significant t-test. It stops short of operational behavior such as assumptions required (normality, equal variances), how paired/subject interact, or what happens if bound is poorly chosen — but the interpretive disclosure is well above average.

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 one-line definition, then cleanly sectioned into when-to-use and when-not-to-use. Slightly redundant at the close, where 'absence of evidence is not evidence of absence' restates the preceding sentence about non-significance, but the repetition is argumentative rather than wasteful.

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 conceptual framing is strong. However, for a 6-parameter statistical tool with zero schema description coverage, leaving `paired`, `subject`, `dv`, and `group` entirely unexplained means an agent cannot reliably construct a paired design call from the definition alone.

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 description coverage is 0%, so the description must compensate for six undocumented parameters; it explains only `bound` (the negligible-difference threshold that must be justified in advance). It says nothing about `name`, `dv`, `group`, or critically the `paired`/`subject` relationship, which for a paired TOST is a real specification risk.

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?

Names the specific procedure (TOST) and its inferential purpose — demonstrating equivalence of two groups — which is meaningfully different from the difference-testing siblings in the catalog. An agent can distinguish this from stat_bayes_ttest or stat_nonparametric_2 without opening the 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?

Provides explicit WHEN TO USE and WHEN NOT TO USE sections, including the key exclusion (not a post-hoc rescue of a non-significant t-test) and the reason TOST answers a different question. This is exactly the routing guidance an agent needs to avoid the most common misuse.

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