Skip to main content
Glama

Kendall tau-b with ties

bpj_pairs_kendall
Read-onlyIdempotent

Count concordant and discordant pairs and correct the denominator for one-sided ties.

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_kendall"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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, so the safety profile is covered. The description adds the genuinely useful behavioral detail that one-sided ties are corrected in the denominator, but says nothing about the returned value, error handling for non-numeric or unequal-length input, or what happens when there are no ties.

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 dense sentence with no filler, front-loaded on the computation. It is efficient, though the brevity crosses into under-specification rather than earning every omission.

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?

With no output schema, the description should say what comes back (tau-b value alone, or with p-value/tie counts) and how x/y must be formatted and paired. Neither is addressed, so an agent cannot predict the result shape or validate inputs for a two-parameter statistical routine.

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%, so the description must carry the burden, and it says nothing about x and y. Only the schema titles ('First/Second numeric series (JSON)') hint that these are JSON-encoded numeric arrays; pairing semantics, equal-length requirement, and tie handling within each series are left entirely undocumented.

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

Purpose3/5

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

The description names the underlying computation (concordant/discordant pair counts with a tie correction), which implies Kendall tau-b, but it never states the actual output (a tau-b coefficient) and leans on the title to supply the statistic name. Among siblings like bpj_pairs_pearson, bpj_pairs_spearman, and bpj_pairs_sign_counts, nothing in the text differentiates when this variant is the right one.

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 or when-not-to-use guidance, and no mention of alternatives such as Pearson, Spearman, or sign counts despite a large family of sibling correlation tools. The only hint is implicit: the tie correction suggests use with ordinal/tied data, which the agent must infer.

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.