Skip to main content
Glama

Stat Plot Rm Corr

stat_plot_rm_corr

Plot repeated-measures correlations with per-participant fit lines to reveal whether the within-subject relationship holds consistently across participants.

Instructions

Plot for a repeated-measures correlation, with a per-participant fit.

WHEN TO USE: alongside stat_rm_correlation, to show whether the within-subject relationship is consistent across participants.

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>",
      "x": "<x>",
      "y": "<y>",
      "subject": "<subject>"
    },
    "name": "stat_plot_rm_corr"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
subjectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about whether the plot is rendered, written to a file, or returned as an object, nor whether it requires a prior fitted model or loaded data. The only behavioral content is the visual claim that each participant gets its own fit line. Side effects and prerequisites are unaddressed.

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?

Two short, front-loaded sentences with the core purpose first and the usage condition second; no filler or repetition. It is efficient, though the brevity is part of why parameter information is absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, but for a four-parameter tool with zero schema description coverage and no annotations the description leaves too much unexplained — what `name` does, that `subject` defines participant grouping, and any rendering or persistence behavior. An agent could plausibly mis-bind the string arguments.

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 four required parameters (`name`, `x`, `y`, `subject`), so the description must compensate and largely does not. 'Per-participant fit' weakly implies `subject` is a grouping variable, and 'relationship' implies `x`/`y` are variable names, but `name` is never explained and no format or constraint guidance is given.

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?

The description uses a specific noun phrase ('Plot for a repeated-measures correlation, with a per-participant fit') that tells an agent exactly what artifact the tool produces, and it names the companion tool `stat_rm_correlation`. It is not quite a 5 because it does not distinguish itself from other plotting siblings such as `stat_plot_paired` or `stat_plot_blandaltman` beyond the correlation framing.

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?

The explicit 'WHEN TO USE' block gives a concrete condition (use alongside `stat_rm_correlation` when checking whether the within-subject relationship is consistent across participants), which is real routing guidance rather than implied usage. There are no when-not conditions or notes about what to do if `stat_rm_correlation` has not been run first.

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