Skip to main content
Glama

Bundle Cannibalization Impact

bpj_bundle_cannibalization_impact
Read-onlyIdempotent

Calculate bundle contribution per sale net of the expected standalone-pair contribution displaced by the bundle.

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": {
      "price": "<price>",
      "priceB": "<priceB>",
      "cost": "<cost>",
      "costB": "<costB>",
      "bundle": "<bundle>",
      "displacement": "<displacement>"
    },
    "name": "bpj_bundle_cannibalization_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
costBYes
priceYes
bundleYes
priceBYes
displacementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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 safety is covered. Beyond that, the description adds no behavioral context: no formula, no sign convention, no currency/units assumption, no note on whether 'displacement' is applied to margin or revenue, and no statement of what the single returned number represents.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity comes at the cost of specification rather than being a model of compact completeness.

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?

This is a six-required-parameter financial calculation with no output schema and no documented formula, so the description should explain the computation and result units. It does neither, leaving the agent unable to predict the returned value or verify the input roles.

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%, so the description carries the burden of explaining the six required numeric inputs, but it explains none of them. In particular it never clarifies that price/cost are item A versus priceB/costB for item B, nor how the displacement percentage enters the calculation. Only the bare JSON 'title' fields give the agent any parameter meaning.

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 gives a specific verb ('Calculate') and a precisely named quantity ('bundle contribution per sale net of the expected standalone-pair contribution displaced'), which is clearly distinct from siblings like bpj_paid_organic_cannibalization. It is clear what family of computation this belongs to, though it never states the actual formula or how the two contribution terms are derived from the six inputs.

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 tool, no prerequisites, and no mention of alternatives such as the paid/organic cannibalization sibling. The agent must infer the use case entirely from the 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.