Skip to main content
Glama

Stat Data Quality Check

stat_data_quality_check

Screen a dataset for missing values, outliers, and distribution shape before analysis; returns per-column missing counts, MAD-based outlier flags, skewness, and kurtosis.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
columnsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on behavior-specific outputs (MAD outlier rule, skewness, kurtosis, per-column missing counts) and explains why results matter for downstream feasibility, but it never states that the call is non-mutating, whether it errors on empty/degenerate columns, or how the specific MAD threshold is configured.

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-loads the one-line purpose, then separates preconditions and return values into labeled lines; every sentence earns its place. The 'Returns' line is mildly redundant given an output schema exists, but it still guides attention to the salient fields.

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?

For a two-parameter diagnostic tool the purpose and workflow placement are complete, and an output schema exists so return values need not be spelled out. However, with 0% schema description coverage the definition leaves the required 'name' parameter and the optional 'columns' filter entirely undefined, which is a real gap for a tool that must be invoked correctly.

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% for both parameters, so the description should compensate and does not: neither 'name' (required) nor 'columns' appears in the text. An agent must guess whether 'name' is a dataset identifier, a file path, or a loaded-object reference, and the meaning of the optional 'columns' subsetting is left entirely to the caller.

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?

States a specific verb and resource ('Screen a dataset') and enumerates exactly what is checked: missingness, outliers, distribution shape. It is clearly a diagnostic/pre-flight tool, distinguishable in kind from analysis tools like stat_anova or stat_linear_regression, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing guidance ('Run this on every new dataset before planning any analysis', 'first thing after loading real data') plus a rationale about feasibility (complete cases per group). Lacks a when-not or a named alternative for the case where the user already knows their data quality.

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