Skip to main content
Glama

Sample covariance

bpj_pairs_sample_covariance
Read-onlyIdempotent

Measure joint sample spread using the n minus one denominator.

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

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?

The annotations already declare this as a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds useful behavioral context by specifying the n-1 denominator, but it does not describe the return value, handling of unequal-length inputs, or edge cases such as missing values.

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?

The definition is a single compact sentence with no wasted wording. It is front-loaded around the core computation, though the phrase 'joint sample spread' is slightly less direct than simply saying sample covariance.

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?

For a simple statistical tool with no output schema and no parameter descriptions, the definition is too thin. An agent still lacks the input format, equal-length requirement, output shape, and edge-case behavior needed to invoke it confidently.

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%, and the description says nothing about the x and y parameters. It does not explain that they are JSON-encoded numeric series, whether they must be equal length, or how paired values are handled, so it fails to compensate for the sparse schema.

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 statistical operation, measuring joint sample spread with the n-1 denominator, which clarifies sample covariance rather than population covariance. It does not explicitly differentiate this tool from related siblings such as Pearson correlation or population covariance, so it is clear but not fully sibling-aware.

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?

The description gives no guidance on when to use sample covariance instead of related tools like correlation, weighted variance, or population covariance. Usage is only implied by the statistical term itself.

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.