Skip to main content
Glama

Stat Qqplot

stat_qqplot

Create a quantile-quantile plot to judge distributional shape and see how data depart from normality alongside a normality test.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
distNonorm
nameYes
columnYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden. It clarifies the interpretive role of the plot versus a p-value, but says nothing about whether the call is read-only, what happens with the default distribution, or how the plot is returned (though an output schema exists). Adequate but not rich.

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?

Three short blocks with front-loaded purpose and labeled guidance sections. Every sentence earns its place and nothing is padded.

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?

Usage guidance is excellent and an output schema covers the return value, but the complete absence of parameter semantics leaves a real gap for a tool with a required column selector and a configurable reference distribution.

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 all three parameters, yet the description never mentions `name`, `column`, or `dist` (which defaults to "norm"). With no schema text and no description text, an agent must guess the meaning of the distribution parameter and where the data comes from.

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?

Names a specific visualization (quantile-quantile plot) and its purpose (judging distributional shape), and implicitly separates it from the normality test it accompanies. It does not distinguish itself from other plotting siblings such as stat_plot_blandaltman or stat_plot_paired, but the plot type itself is distinctive enough for correct selection.

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?

Has explicit WHEN TO USE (alongside every normality test) and WHEN NOT TO USE (not as the only check — report the test statistic too) sections. The reasoning is also given, so an agent understands not just the condition but why it matters.

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