Skip to main content
Glama

Stat Plot Blandaltman

stat_plot_blandaltman

Plot a Bland-Altman chart to assess agreement between two measurement methods, ideal for method comparison, test-retest, or new device validation studies.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
agreementNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 disclosure burden. It conveys that this is an analytical plot for agreement rather than a mutation, and the presence of an output schema covers return values, but it says nothing about whether limits of agreement are configurable, what the resulting plot contains, or any assumptions/prerequisites. Adequate but thin for a no-annotation tool.

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 labelled blocks with the definition front-loaded and the routing guidance clearly separated. No filler sentences; every line carries decision-relevant information.

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?

Output schema exists so return values need not be explained, and the usage routing is complete. However, for a four-parameter statistical tool with zero schema documentation, leaving 'agreement' and 'name' entirely unexplained is a real gap an agent would hit when constructing the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description is the only source of semantics. The framing of "two measurement methods" implicitly maps to x and y, which is genuine added meaning, but the required "name" argument and the "agreement" multiplier (default 1.96, presumably the SD multiplier for limits of agreement) are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific plot type and states exactly what it measures ("agreement between two measurement methods"), which is a distinct statistical purpose from the correlation-oriented siblings. An agent can identify this as the method-comparison plot without opening the schema.

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?

Provides an explicit WHEN TO USE list (method comparison, test-retest, new device vs. criterion) and an explicit WHEN NOT TO USE that names the correct alternative (scatter plot with correlation) for association questions. This is the full when/when-not/alternative pattern.

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