gpower-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 Supply |
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.