Skip to main content
Glama

Holdout Incremental Acquisition Cost

bpj_holdout_incremental_acquisition_cost
Read-onlyIdempotent

Use the holdout conversion rate to estimate baseline treatment conversions and calculate cost per positive incremental conversion.

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": {
      "exposed": "<exposed>",
      "conversionsA": "<conversionsA>",
      "holdout": "<holdout>",
      "conversionsB": "<conversionsB>",
      "spend": "<spend>"
    },
    "name": "bpj_holdout_incremental_acquisition_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
spendYes
exposedYes
holdoutYes
conversionsAYes
conversionsBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 fully covered and the description adds the core behavior (holdout-derived baseline). However, with no output schema, the description should disclose the return shape, the currency/units of spend, and edge-case behavior when incremental conversions are zero or negative (division by zero or a nonsensical negative cost) — the phrase 'cost per positive incremental conversion' hints at this but never resolves it.

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 dense sentence that front-loads the method (holdout rate) before the output (cost per incremental conversion), with no filler. It is efficient, though the compressed phrasing trades away the disambiguation the parameters need.

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 five-required-parameter math tool with no output schema and zero schema description coverage, so the description bears the full documentation burden and under-delivers. It omits the parameter-to-role mapping, output shape, spend units, and behavior for zero or negative incremental conversions — gaps an agent would hit immediately on first call.

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 properties carry only bare titles, so the description must carry all semantic weight; it does not. It conveys the roles of holdout and spend conceptually, but leaves the critical A/B ambiguity — which of conversionsA and conversionsB is treatment versus holdout — unresolved, and never states units for spend or that exposed/holdout are audience sizes paired with those conversion counts.

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?

States a specific computation: derive baseline treatment conversions from the holdout conversion rate, then compute cost per positive incremental conversion. That is a clear verb-plus-result, and it distinguishes this from the many other bpj_* cost calculators by naming the holdout-based incrementality method. It stops short of a 5 because it never explicitly maps its own parameter names (e.g. which of conversionsA/conversionsB is treatment vs. holdout) or states what it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The described formula implies the use case (measuring incremental acquisition efficiency against a holdout), but there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling cost tools. An agent must infer applicability from the calculation itself rather than from stated guidance.

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.