Skip to main content
Glama

Weighted population variance

bpj_pairs_weighted_variance
Read-onlyIdempotent

Compute weighted squared deviations from the weighted population mean.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. Beyond that the description adds almost nothing: it does not say how weights are normalized, whether the result is population-only (no sample correction), or what happens with mismatched series lengths. For a statistical computation tool with zero annotation gaps, the description should carry more of the numeric contract.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good. But the brevity comes at the cost of necessary specification rather than from efficient expression.

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, two undocumented string-encoded JSON parameters, and no stated weight convention, the definition is not sufficient for an agent to call this correctly. It omits input encoding, length alignment, and the exact return value.

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% (the two parameters carry only titles like 'First numeric series (JSON)'), so the description must compensate and it does not. It never explains that x and y are JSON-encoded numeric arrays, that they must be equal length, or which one acts as the weight vector.

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 computation (weighted squared deviations about the weighted population mean) and the name/title supply the term 'variance', so the intent is recoverable. However, it never states which of the two series is the data and which supplies the weights, which is the central semantic distinction from sibling tools like bpj_pairs_weighted_mean.

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 use this rather than siblings such as bpj_pairs_weighted_mean or bpj_pairs_weighted_median, and no prerequisite or exclusion is stated. The agent must infer the choice 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.