Skip to main content
Glama

Column sample covariance matrix

bpj_matrix_column_covariance
Read-onlyIdempotent

Treat rows as observations and compute pairwise sample covariance of grid columns.

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": {
      "matrix": "<matrix>"
    },
    "name": "bpj_matrix_column_covariance"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered structurally. The description adds the meaningful behavioral detail that observations are rows and variables are columns, but it says nothing about output shape, minimum row requirements, or how non-numeric or ragged input is handled.

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?

One sentence, front-loaded with the key orientation cue before the operation, with no filler. It is efficient, though the terseness leaves no room for the operational details an agent needs.

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 single-parameter, read-only, idempotent computation, the annotations and schema title carry much of the load, and no output schema means return values need not be explained. Still, the definition omits the shape of the result (a symmetric column-by-column matrix), the sample-vs-population denominator, and any input validation behavior, which are reasonable expectations for a statistical tool.

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%, and the single parameter is a JSON-encoded numeric matrix. The description compensates partially by fixing the row/column interpretation, which is genuinely decision-relevant, but it does not describe the expected serialization format, shape constraints, or how many observations are required for a sample covariance.

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 operation and resource: 'compute pairwise sample covariance of grid columns'. Combined with the title 'Column sample covariance matrix', an agent knows exactly what the tool returns conceptually. It does not explicitly differentiate from the sibling bpj_pairs_sample_covariance or bpj_matrix_column_standardize, so it falls short of a 5.

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 prerequisites, and no mention of when another tool would be preferred. The phrase 'treat rows as observations' implies the input orientation but not the choice conditions between this and related matrix/covariance siblings.

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.