Skip to main content
Glama
gpower-mcp

gpower-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_testsA

List every statistical test this engine implements, with its effect-size metric, design (one- or two-group) and supported analysis types.

describe_testB

Describe one test: its exact G*Power menu title, effect-size metric, extra parameters, and which analysis types it supports.

power_analysisA

Run one power analysis and return the full numeric result plus ready-to-paste prose.

solve_for: "n" -> smallest sample size reaching power (a priori) "power" -> achieved power of an explicit design (post hoc) "alpha" -> alpha needed to reach power (criterion) "effect_size" -> smallest detectable effect (sensitivity) "compromise" -> alpha and power implied by beta_alpha_ratio

Supply n1+n2 or n(+allocation_ratio) for the two-group test and n otherwise. predictors applies to ttest-regression-coef; df to ttest-generic.

compute_effect_sizeA

Convert raw descriptive statistics into the standardised effect size a test needs.

Calculators: d-two-independent-means mean1, mean2, sd1, sd2 [, equal_n, n1, n2] dz-matched-pairs mean1, mean2, sd1, sd2, correlation dz-from-difference mean_difference, sd_difference d-one-sample mean, reference, sd f2-from-r-squared r_squared f2-from-partial-r-squared partial_r_squared r-from-d-balanced d

power_curveB

Tabulate power against sample size -- useful for showing a user the trade-off instead of a single number. Capped at 500 rows.

engine_provenanceA

Report engine version, the specification it implements, and the documented behavioural findings it encodes. Use this when a user asks how trustworthy the numbers are or where they come from.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct role: discovery, single-test description, single power analysis, power curve tabulation, effect-size conversion, and provenance reporting. The only near-overlap is between power_analysis and power_curve, but their descriptions make the single-result versus tabulated trade-off explicit.

Naming Consistency4/5

All names use snake_case consistently, and most are readable verb-led or domain-specific names. However, the set mixes verb_noun names like list_tests and compute_effect_size with noun phrases like power_curve and engine_provenance, so it is not a strict uniform pattern.

Tool Count5/5

Six tools is well within the ideal range for a focused statistical power engine. Each tool covers a distinct part of the workflow, and none feels redundant or padded.

Completeness5/5

The surface covers test discovery, detailed test metadata, power analysis across all solve-for modes, power curves, effect-size conversion, and provenance. For a G*Power-style engine, this is a complete lifecycle with no obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessSyncing