Skip to main content
Glama

Pearson linear correlation

bpj_pairs_pearson
Read-onlyIdempotent

Measure linear association from the covariance of paired observations.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds the computational basis (computed from covariance of paired observations), which is mild extra context. It omits anything about assumptions (linearity, outlier sensitivity), error behavior for mismatched lengths, or the range of the returned coefficient.

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 or redundancy. Its brevity is efficient, though it shades into under-specification rather than crispness.

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 is returned (a coefficient in [-1, 1]) and how degenerate inputs are handled. Neither the JSON-string input encoding nor the return value is described, leaving an agent to guess on both the call and the result.

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 does not. Critically, both parameters are strings holding JSON arrays (maxLength 12000), a non-obvious encoding that the description never mentions; an agent could easily pass a native array and fail.

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 states a specific measurement operation ('measure linear association') over a specific input type ('paired observations'), and combined with the name/title an agent can identify this as Pearson correlation. It does not, however, contrast itself with the rank-based siblings such as bpj_pairs_spearman or bpj_pairs_kendall, so the differentiation is only implicit.

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 guidance on when to choose this over spearman/kendall/cosine, nor any stated preconditions (equal-length series, numeric-only values, minimum sample size). The agent must infer all selection criteria from the name alone.

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.