Skip to main content
Glama

Campaign Break-Even ROAS

bpj_campaign_break_even_roas
Read-onlyIdempotent

Compare campaign ROAS with break-even ROAS using the contribution margin before ad 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": {
      "sales": "<sales>",
      "adSpend": "<adSpend>",
      "contributionMargin": "<contributionMargin>"
    },
    "name": "bpj_campaign_break_even_roas"
  }
}

Input Schema

NameRequiredDescriptionDefault
salesYes
adSpendYes
contributionMarginYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structured data. The description adds one genuinely useful methodological detail: the comparison uses contribution margin measured before ad spend. It does not disclose the comparison formula or how the result is presented (e.g., ratio, delta, or pass/fail), which 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the methodological qualifier placed at the end, no filler or repetition. It is efficient, though the terseness is part of why so little guidance is conveyed.

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?

For a three-required-parameter calculator with no output schema and no parameter descriptions, the description should explain what is returned and how the inputs combine. It omits the return shape entirely (comparison result, break-even threshold, or verdict), so an agent cannot predict the outcome of a 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%, so the description must carry parameter meaning, and it only partially does. It clarifies that contribution margin is taken before ad spend, but gives no unit guidance for revenue versus ad spend or confirmation that contributionMargin is a percentage (0-100) rather than a fraction, leaving the relation between the three required inputs under-explained.

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 verb (compare) and two specific quantities (campaign ROAS vs. break-even ROAS), plus the input basis (contribution margin before ad spend). An agent can tell this is a marketing-economics calculator. It stops short of distinguishing itself from nearby analytics siblings such as bpj_break_even_units or bpj_customer_ltv_cac.

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 explicit when-to-use, when-not-to-use, or prerequisite guidance. The name and one-line description imply a break-even analysis context, but nothing tells the agent when this tool is the right choice over alternative ROAS or unit-economics tools.

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.