Pingouin-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINGOUIN_MCP_CONFIG | No | Path to a config file. | ~/.pingouin-mcp/config.json |
| PINGOUIN_MCP_TIMEOUT | No | Seconds before a tool call is abandoned. | 300 |
| PINGOUIN_MCP_DATA_DIR | No | Directory searched by data tools. | current directory |
| PINGOUIN_MCP_RESULTS_DIR | No | Where figures are written. | ~/.pingouin-mcp/results |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stat_load_dataA | Load a tabular dataset (CSV/TSV/Excel/JSON/Parquet/SPSS) into the session. Use this as the first step for any dataset stored as a file. The loaded
object is stored under When to use: at the start of an analysis session, once per dataset.
When NOT to use: if the data are already in the session (check with
|
| stat_make_dataframeA | Build a DataFrame from a {column: [values]} mapping. Use this for worked examples, sanity checks, and illustrating a method with hypothetical data. When NOT to use: never for real analysis — fabricated data must not enter an analysis of real results. |
| stat_describe_dataA | Descriptive statistics, optionally broken down by group. Use this to report the sample before any inference: means, SDs, medians and group sizes are expected in every results section. When to use: immediately after loading, and again when writing up.
When NOT to use: as a substitute for checking assumptions — use
|
| stat_data_quality_checkB | Screen a dataset for missingness, outliers and distribution shape. Run this on every new dataset before planning any analysis: it determines whether the planned analysis is even possible (e.g. a between-subjects test needs enough complete cases per group). When to use: first thing after loading real data. Returns: missing counts per column, outliers flagged by the robust MAD rule, skewness and kurtosis. |
| stat_decision_assistantA | Recommend which statistical test fits a study design — call this BEFORE running a test. This exists because choosing the wrong test is the most consequential error in statistical analysis, and it invalidates the p-value rather than merely producing a suboptimal number. If you are not certain which test applies, call this first. |
| stat_assumption_reportA | 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. |
| stat_normality_testA | Test whether a variable is normally distributed, optionally within each group. When to use: before any parametric test (t-test, ANOVA, Pearson correlation). When NOT to use: as a gatekeeper that alone decides parametric vs non-parametric. With large n the test detects trivial deviations; with small n it has low power. Judge with the QQ plot and skewness too. |
| stat_homogeneity_testA | Test equality of variances across groups. When to use: before an independent-samples t-test or a one-way ANOVA. When it fails: use Welch's t-test or Welch's ANOVA, which do not assume equal variances. |
| stat_sphericity_testA | Mauchly's test of sphericity for a repeated-measures factor with 3+ levels. When to use: before a repeated-measures ANOVA with three or more conditions. When it fails: report the Greenhouse-Geisser corrected p-value and the epsilon. The uncorrected F is anti-conservative when sphericity is violated. Not applicable with only two levels — a paired t-test needs no sphericity assumption. |
| stat_ttestA | t-test: independent samples, paired, or one-sample. WHEN TO USE
WHEN NOT TO USE
Always report the effect size (Cohen's d, given in the output) and the CI. |
| stat_nonparametric_2A | Mann-Whitney U (independent) or Wilcoxon signed-rank (paired) — two groups, no normality assumption. WHEN TO USE
WHEN NOT TO USE
Report the rank-biserial correlation (RBC) as the effect size — the p-value alone says nothing about magnitude. |
| stat_bayes_ttestA | Bayesian t-test — quantifies evidence for the null as well as the alternative. WHEN TO USE
WHEN NOT TO USE
Report BF₁₀ and BF₀₁, and state the prior scale (r). |
| stat_anovaA | One-way ANOVA — three or more independent groups, continuous outcome. WHEN TO USE
WHEN NOT TO USE
A significant omnibus F says only that some groups differ, not which. Always
follow with |
| stat_welch_anovaA | Welch's ANOVA — three or more groups without the equal-variance assumption. WHEN TO USE: Levene's test is significant, or group sizes and variances differ. WHEN NOT TO USE: when variances are equal — the standard ANOVA is more powerful. Note: Welch's ANOVA does not yield the usual η²; report ω² or use pairwise effect sizes with a correction. |
| stat_rm_anovaA | Repeated-measures ANOVA — one within-subjects factor with three or more levels. WHEN TO USE: the same participants measured under 3+ conditions. WHEN NOT TO USE:
Always check sphericity first ( |
| stat_mixed_anovaB | Mixed-design ANOVA — one between-subjects factor crossed with one within-subjects factor. WHEN TO USE: e.g. two groups measured at three time points; group × time designs. Read the interaction first. A significant interaction means the effect of one factor depends on the level of the other, and the main effects must not be interpreted in isolation. |
| stat_ancovaA | ANCOVA — compare groups while statistically controlling a continuous covariate. WHEN TO USE: a continuous variable is expected to influence the outcome and differs between groups (e.g. age, baseline score). WHEN NOT TO USE — two conditions that are frequently violated:
The tool tests homogeneity of regression slopes automatically and tells you if ANCOVA is inappropriate. |
| stat_nonparametric_kA | Kruskal-Wallis (independent) or Friedman (repeated) — three or more groups, no normality assumption. WHEN TO USE: 3+ groups with ordinal outcomes, or continuous outcomes where normality is badly violated. WHEN NOT TO USE: when the parametric assumptions hold — the rank test is less powerful. Follow a significant result with |
| stat_pairwise_testsB | Pairwise comparisons with optional multiple-comparison correction. WHEN TO USE
WHEN NOT TO USE: as an exploratory scan of every possible pair without a correction — that is p-hacking. Set |
| stat_pairwise_tukeyA | Tukey HSD or Games-Howell post-hoc tests after a one-way ANOVA. WHEN TO USE
WHEN NOT TO USE: for within-subjects designs — use |
| stat_multicomp_correctionA | Correct a list of p-values for multiple comparisons. WHEN TO USE: when you have a set of p-values computed outside Pingouin, or when applying a correction across several tests reported together. Choosing a method:
State the method by name in the write-up; "we corrected for multiple comparisons" without naming the method is not reproducible. |
| stat_correlationA | Correlation between two continuous variables. WHEN TO USE
WHEN NOT TO USE
Always report r (or rho) with its CI, not just the p-value. |
| stat_partial_correlationA | Partial correlation — association between two variables after removing covariates. WHEN TO USE: a third variable plausibly drives both x and y, and you want the association net of it. WHEN NOT TO USE: as a substitute for modelling. If several covariates are involved, regression gives a clearer picture. Partial correlation also assumes the covariate is measured without error. |
| stat_rm_correlationA | Repeated-measures correlation — the correct correlation for within-subject data. WHEN TO USE: whenever each participant contributes more than one observation and you want the association between x and y. WHEN NOT TO USE: when each participant appears once — use Why it matters: a standard Pearson correlation on repeated measures is inflated by between-subject differences. rm_corr reports the within-subject association, which is usually the quantity of interest, and tests whether within- and between-subject slopes differ. |
| stat_correlation_matrixA | Correlation matrix across several variables, optionally with p-value correction. WHEN TO USE: exploratory screening across a set of variables, or a correlation table for a paper. WHEN NOT TO USE: as a basis for causal claims, or when the number of variables is large relative to n — correlations become unstable. With more than two variables, always pass |
| stat_distance_correlationA | Distance correlation — detects any dependence, linear or not. WHEN TO USE
WHEN NOT TO USE: as a replacement for interpretable effect sizes — the coefficient has no simple direction or magnitude reading. Bootstrap-based, so it is slower; reduce |
| stat_linear_regressionA | Ordinary least-squares regression with coefficients, CIs and model fit. WHEN TO USE: continuous outcome predicted from one or more continuous or dummy-coded predictors; or when adjusting for covariates in a continuous-outcome model. WHEN NOT TO USE:
The output includes R² and adjusted R². Check the assumptions listed in the output before interpreting coefficients; a significant coefficient is not evidence of a causal effect. |
| stat_logistic_regressionA | Binary logistic regression with odds ratios and confidence intervals. WHEN TO USE: a binary outcome (yes/no, present/absent) predicted from one or more variables. WHEN NOT TO USE:
An odds ratio is not a risk ratio: for common outcomes it exaggerates the effect. Report predicted probabilities alongside when the substantive question is about risk. |
| stat_mediationA | Mediation analysis — does x affect y through m? WHEN TO USE: a plausible causal chain x → m → y, with m measured after x and before y, and a theoretical reason to expect transmission. WHEN NOT TO USE
The indirect effect's bootstrap CI excluding zero is the evidence for mediation. Report that CI, not the Sobel test. |
| stat_effect_sizeA | Effect size with a confidence interval for a two-group comparison. WHEN TO USE: alongside every t-test and every pairwise comparison. A p-value says whether an effect is distinguishable from zero; the effect size says whether it matters. WHEN NOT TO USE: for 3+ groups in a single call — use the effect sizes
reported by ANOVA or by Note on paired designs: the standardiser is the SD of the difference scores, not the pooled SD. Cohen's d and dz are different quantities — state which you report. |
| stat_power_analysisA | Power analysis — solve for whichever of effect size / n / power / alpha is omitted. WHEN TO USE
WHEN NOT TO USE: to compute "observed power" from the current sample's effect size and then interpret it — that is circular and adds nothing to the p-value. Supply exactly three of the four quantities; the fourth is solved for. |
| stat_cronbach_alphaA | 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
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. |
| stat_intraclass_correlationA | Intraclass correlation — agreement or consistency between raters or measurements. WHEN TO USE: inter-rater reliability, test-retest reliability, agreement between measurement devices. WHEN NOT TO USE: as a substitute for Bland-Altman when the question is whether two methods agree in absolute terms — ICC is bounded by the range of the sample and can look excellent while agreement is poor. Choosing the form matters and is often got wrong:
|
| stat_equivalence_testA | 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 |
| stat_chi2_independenceA | Chi-square test of independence between two categorical variables. WHEN TO USE: two categorical variables from independent observations. WHEN NOT TO USE
Report Cramér's V as the effect size. |
| stat_chi2_mcnemarA | McNemar's test — paired categorical data (before/after, matched pairs, twins). WHEN TO USE: the same units contribute a categorical value under two conditions (pre/post intervention, two raters, matched pairs). WHEN NOT TO USE: for independent groups — use Only the two discordant cells contribute to the statistic. |
| stat_plot_pairedA | Paired-data plot — one line per participant across conditions. WHEN TO USE: reporting any within-subjects comparison. It shows the participant-level change that the test actually analyses. WHEN NOT TO USE: for independent groups — a boxplot or raincloud plot is appropriate there. A bar chart of means hides participants moving in opposite directions, which is exactly the pattern that makes a mean difference misleading. |
| stat_plot_blandaltmanA | Bland-Altman plot — agreement between two measurement methods. WHEN TO USE: method comparison studies, test-retest agreement, comparing a new device or scale against a criterion. WHEN NOT TO USE: when the question is association rather than agreement — for that, use a scatter plot with a correlation. |
| stat_qqplotA | Quantile-quantile plot for judging distributional shape. WHEN TO USE: alongside every normality test. The plot shows how the data depart from normality, which the test's p-value cannot tell you. WHEN NOT TO USE: as the only check — report the test statistic too. |
| stat_plot_rm_corrB | Plot for a repeated-measures correlation, with a per-participant fit. WHEN TO USE: alongside |
| stat_session_infoA | List the datasets and results currently held in the session. Call this when unsure what data are available, or after loading several datasets, to confirm the names the other tools expect. |
| stat_reset_sessionA | Clear all datasets, results and figures, starting a fresh session. WHEN TO USE: before starting a genuinely separate analysis, to avoid reading stale objects. WHEN NOT TO USE: casually — loaded data are lost. |
| stat_run_codeA | Execute arbitrary Python against the session namespace — the escape hatch. Use this for anything the structured tools do not cover: custom recoding, a Pingouin function not exposed as a tool, or a bespoke plot. Pre-bound names: The value of a trailing expression is returned. Matplotlib figures are saved automatically and their paths returned. WHEN TO USE: beyond the structured tools. WHEN NOT TO USE: for routine analyses — the structured tools report assumptions and effect sizes that a bare call would omit. |
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 43 tools
Almost every tool targets a distinct statistical procedure, and the WHEN TO USE / WHEN NOT TO USE blocks actively route the agent between near-neighbours (e.g. stat_ttest vs stat_bayes_ttest vs stat_equivalence_test). The main soft spots are stat_pairwise_tests vs stat_pairwise_tukey, and stat_assumption_report vs the individual normality/homogeneity/sphericity checks, which overlap in purpose though the descriptions explain the aggregate-vs-single distinction.
Every one of the 43 tools uses the same `stat_` prefix plus snake_case verb_noun form (stat_load_data, stat_normality_test, stat_rm_anova). Even abbreviations like stat_ttest and stat_qqplot fit the pattern predictably.
43 tools is well past the range where an agent can reliably scan and select; the statistics domain is broad, but the surface is split very finely (separate tools for sphericity, homogeneity, normality, Tukey, Games-Howell, etc.). Many could be consolidated into parameterised tools without losing capability.
Coverage is strong across descriptive stats, assumption checks, parametric/non-parametric tests, regression, reliability, power and plotting, with stat_run_code as an explicit escape hatch for gaps. However, several analyses the descriptions themselves recommend are not exposed as tools (mixed-effects models, ordinal regression, Firth/penalised regression, factor analysis, and basic group plots like boxplots/rainclouds), and there is no export/report-writing tool.