Skip to main content
Glama

Bland-Altman agreement limits

bpj_pairs_bland_altman
Read-onlyIdempotent

Report average second-minus-first bias and agreement limits at 1.96 sample standard deviations.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "bpj_pairs_bland_altman"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description usefully pins the exact estimator (mean of second-minus-first, limits at 1.96 sample SD), but says nothing about equal-length requirements, handling of unparseable JSON, or failure behavior — gaps that matter for a computation tool.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is part of why preconditions and input format go unstated.

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 simple two-series computation with no output schema, the description covers what is computed but omits the input contract (JSON arrays, equal length, numeric coercion) that an agent needs to call it successfully the first time. Adequate but with a clear gap.

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 coverage is 0% and the two parameters only carry titles ('First numeric series (JSON)', 'Second numeric series (JSON)'). The description does add one genuinely useful semantic — 'second-minus-first' fixes the sign convention and thus which parameter is the reference — but it does not explain the JSON array encoding, the requirement that x and y be equal length, or numeric coercion.

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 names a specific statistical procedure (Bland-Altman) and its two outputs — average bias and 1.96-SD agreement limits — so an agent can tell it apart from generic correlation or error siblings like bpj_pairs_pearson or bpj_pairs_rmse. It does not explicitly state that it operates on two paired numeric series, leaving that to the schema titles.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when a different agreement/method-comparison tool (e.g. bpj_pairs_deming, bpj_pairs_linear_fit) would be preferable, and no stated preconditions. The agent must infer the use case entirely from the statistical term 'Bland-Altman'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.