Skip to main content
Glama

Cumulative gains by score

bpj_pairs_cumulative_gains
Read-onlyIdempotent

Rank by descending score and report cumulative nonnegative outcome share at each tied-score boundary.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: it specifies descending ranking, tie-boundary grouping, and that only nonnegative outcomes contribute to the share. It does not say how negative outcomes are handled (dropped or included in the denominator) or what the returned structure looks like, so it stops short of full transparency.

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 dense sentence that front-loads the ranking step before the reporting step, with no filler. It is efficient, though its terseness contributes to the unresolved operand mapping.

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 two-parameter read-only computation with no output schema, the description covers the core algorithm but omits the x/y role assignment and the shape of the result. An agent could guess the intended usage but could easily pass score and outcome in the wrong order.

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 only labels are 'First numeric series (JSON)' and 'Second numeric series (JSON)'. The description introduces the concepts of score and outcome but never maps them onto x and y, leaving the single most important parameter question unresolved. This is a case where the description needed to compensate for the schema and did not.

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 computation: rank a series by descending score and report cumulative nonnegative outcome share at tied-score boundaries, which is clearly a cumulative-gains/lift style analysis and distinguishes it from siblings like bpj_pairs_pearson or bpj_series_cumulative_sum. The gap is that it never states which of the two inputs is the score and which is the outcome, so the purpose is clear but the operand roles are not.

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 alternatives such as bpj_series_cumulative_share or bpj_pairs_spearman, despite many plausible siblings. The agent must infer the appropriate context entirely from the tool name and one sentence.

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.