Skip to main content
Glama

Stat Cronbach Alpha

stat_cronbach_alpha

Computes Cronbach's alpha to measure internal consistency reliability of a multi-item scale in your sample, reporting confidence intervals and item count for questionnaire reliability assessment.

Instructions

Cronbach's alpha — internal consistency of a multi-item scale.

WHEN TO USE: reporting the reliability of a questionnaire or scale in the current sample.

WHEN NOT TO USE

  • As the sole evidence of unidimensionality — alpha can be high for a multidimensional scale. Confirm with factor analysis.

  • For binary items (use KR-20) or for inter-rater agreement (use ICC).

Alpha rises with the number of items regardless of their quality: report the item count and the CI, and consider the mean inter-item correlation.

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

Input Schema

NameRequiredDescriptionDefault
ciNo
nameYes
itemsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does add substantive behavior: alpha inflates with item count regardless of quality, and the guidance to report item count, CI, and mean inter-item correlation. It does not describe the returned values, but an output schema is present, so that omission is acceptable.

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?

Front-loaded one-line definition, then clearly delimited usage blocks, then a short statistical caveat paragraph. Every sentence carries decision-relevant information; nothing is repeated from structured fields.

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?

A low-complexity computation with an output schema, so return values need not be described; usage, alternatives, and interpretive caveats are all covered. The remaining gap is the unexplained input parameter semantics, which matters because the schema provides no descriptions.

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%, so the description must compensate, and it only partly does: the CI parameter is referenced ('report the item count and the CI'). The critical ambiguity of 'items' (an array of strings — are these column names, item labels, or response values?) and the meaning of 'name' are left entirely unexplained 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?

The opening line names the statistic and its target construct ('internal consistency of a multi-item scale'), which is specific enough to distinguish it from most siblings. It further separates itself from KR-20 and ICC in the exclusions, though the computing verb itself is only implied.

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 and WHEN NOT TO USE blocks, each negative case paired with the correct alternative (KR-20 for binary items, ICC for inter-rater agreement, factor analysis for unidimensionality). An agent can route correctly without any inference.

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