Skip to main content
Glama

Weighted median by cumulative weight

bpj_pairs_weighted_median
Read-onlyIdempotent

Sort by value and select the first observation reaching half the total weight.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds algorithmic detail beyond that (ordering by value, halving total weight), but omits tie-breaking behavior, handling of zero/negative weights, and what the returned observation looks like.

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?

A single sentence with no filler is well front-loaded, but it is under-specified for a two-parameter tool rather than genuinely concise; the brevity costs clarity.

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 and zero schema description coverage, the description should clarify the x/y roles and the result shape. It leaves the parameter mapping and return value unspecified, which is not enough for an agent to call it correctly without guessing.

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%, so the description carries the full burden, yet it never says which of x and y is the value series and which is the weight series. It also omits the expected JSON-array string format implied only by the schema titles.

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 explains the algorithm (sort by value, take the first observation crossing half the total weight) but never names the operation as a weighted median or states a verb+resource, so the agent must infer purpose from the tool name. It does not distinguish itself from siblings such as bpj_pairs_weighted_mean or bpj_series_moving_median.

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 a weighted median instead of the many sibling median/weighted tools, and no stated preconditions or exclusions. The agent gets an algorithm but no selection criteria.

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.