Skip to main content
Glama

Paid Organic Cannibalization

bpj_paid_organic_cannibalization
Read-onlyIdempotent

Deduct the paid-attributed orders expected to convert organically and value only incremental contribution against media spend.

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": {
      "paidOrders": "<paidOrders>",
      "organic": "<organic>",
      "profit": "<profit>",
      "spend": "<spend>"
    },
    "name": "bpj_paid_organic_cannibalization"
  }
}

Input Schema

NameRequiredDescriptionDefault
spendYes
profitYes
organicYes
paidOrdersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 openWorldHint=false, so the safety profile is fully covered. The description adds that the tool performs an incremental-contribution valuation against media spend, but says nothing about the result shape or edge cases (e.g., organic share of 100%, zero spend).

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 redundancy. It is dense but efficient; the only weakness is that compression costs clarity on the actual formula.

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 four required numeric parameters, no output schema, and no parameter descriptions, the definition should explain the output and the computation. Instead it gives one high-level sentence, leaving the agent unable to predict the returned value or verify correct invocation.

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%; only short titles exist ('Share expected to buy organically (%)', 'Pre-ad contribution per incremental order'). The description references paid orders, organic conversion, and spend, but never explains the role of the 'profit' parameter or how the four inputs combine, so it does not compensate for the coverage gap.

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 a specific analytical operation — deducting organically-converting paid orders and valuing only incremental contribution against spend — so an agent can infer it is a cannibalization adjustment calculator. However, it never states the computation precisely or distinguishes itself from the sibling 'bpj_bundle_cannibalization_impact', leaving the exact transformation ambiguous.

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 the bundle cannibalization tool. The agent must infer the context (paid media measurement) entirely from the sentence itself.

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.