Skip to main content
Glama

Acquisition Cost Including Commission

bpj_fully_loaded_new_account_cost
Read-onlyIdempotent

Allocate acquisition spending plus commissions on new contract value across newly acquired accounts.

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": {
      "acq": "<acq>",
      "commission": "<commission>",
      "termValue": "<termValue>",
      "newAccounts": "<newAccounts>"
    },
    "name": "bpj_fully_loaded_new_account_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
acqYes
termValueYes
commissionYes
newAccountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/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, openWorldHint=false, so safety is covered and the bar is lower. However, this is a computation tool whose core behavior is the formula, and the description does not disclose it: it does not say whether commission is applied as a percentage of termValue, whether the total is divided by newAccounts, or whether mixed time bases (monthly acquisition vs. contract value) are normalized. That omission is the main behavioral gap.

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?

One front-loaded sentence with no filler, which is structurally clean. But for a four-parameter formula tool it is undersized rather than concise; the brevity comes at the cost of the information an agent needs to invoke it correctly.

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?

There is no output schema, so the description would need to explain what is returned (per-account cost, total, currency, time basis), and it does not. With no formula, no units, and no return description, the definition is not complete enough for a computation tool of this shape.

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 all four parameters are required, so the description must carry the load. It does tie commission to new contract value and acquisition spending to new accounts, which adds some relational meaning. But it leaves the critical ambiguities unresolved: that acq is monthly while termValue is a contract value, that commission is a percentage, and how newAccounts acts as the denominator.

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 the inputs (acquisition spending, commissions, new contract value, new accounts) and the notion of allocating them, so the general purpose is inferable. But 'allocate ... across' is vague about the actual result: it never says the output is a per-account fully loaded cost, nor how the pieces combine. No sibling is named or contrasted, so an agent cannot distinguish this from bpj_holdout_incremental_acquisition_cost or bpj_affiliate_commission_clawback on the description alone.

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 statement, no prerequisite, and no mention of an alternative tool or when this calculation is inappropriate. The agent is left to infer the use case entirely from the tool name.

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.