Skip to main content
Glama

Break-Even Units

bpj_break_even_units
Read-onlyIdempotent

Find the minimum whole units needed to cover fixed costs at a given price and variable unit cost.

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": {
      "fixedCost": "<fixedCost>",
      "price": "<price>",
      "unitCost": "<unitCost>"
    },
    "name": "bpj_break_even_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
unitCostYes
fixedCostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add one genuinely useful behavioral detail — results are rounded up to whole units — but says nothing about what happens when price is at or below unitCost, where the computation is undefined or infinite.

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 well-formed sentence with the outcome front-loaded and no filler. It is efficient, though it leaves no room for the caveats a formula tool needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter arithmetic tool with no output schema, this is close to adequate — the operation and rounding behavior are clear. It falls short on the degenerate case (price ≤ unitCost) and on the shape of the returned value, which the description never states.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 the load; it does map its three inputs to fixed cost, unit price, and variable unit cost in plain language. However, it adds no units/currency conventions or constraints beyond the schema's numeric ranges, so the compensation is only partial.

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 ('minimum whole units needed to cover fixed costs') with the inputs it depends on, so the agent knows exactly what it returns. It does not distinguish itself from the sibling bpj_campaign_break_even_roas, which is also a break-even calculation, so an agent must infer the difference from the name 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 guidance on when to use this versus the ROAS break-even sibling, and no prerequisites stated. The description also omits the key precondition that price must exceed unitCost for a break-even to exist.

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.