Skip to main content
Glama

TrueCalci

by com.truecalci

breakeven_margin

Calculate cost-volume-profit break-even thresholds in units and revenue, contribution margin ratio, operational margin of safety, and degree of operating leverage (DOL).

Behavior: Deterministic, idempotent calculation with zero external side effects. Computes Unit Contribution Margin = unitPrice - unitVariableCost; Contribution Margin Ratio = CM / unitPrice; Break-Even Units = fixedCosts / CM; Break-Even Revenue = Break-Even Units * unitPrice. If expected units sold is provided, computes Margin of Safety = (expectedUnits - breakEvenUnits) / expectedUnits and Degree of Operating Leverage. Returns detailed breakdown.

Usage Guidelines: Use for pricing strategy, manufacturing and SaaS unit economics, and operational risk appraisal. Do not use for hourly freelance billing rate minimums; use billable_floor instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitPriceYesSelling price per individual product or service unit in currency units. Must be greater than unitVariableCost.
fixedCostsYesTotal periodic fixed operating overhead costs in currency units (rent, salaries, software). Must be positive.
unitVariableCostYesDirect variable cost incurred per unit produced or delivered in currency units. Must be non-negative.
expectedUnitsSoldNoProjected sales volume in units to evaluate operational margin of safety and operating leverage.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / expectedUnitsSold / description
      Previous value: -"Projected unit sales volume for margin of safety analysis"New value: +"Projected sales volume in units to evaluate operational margin of safety and operating leverage."
    • changedInput schema / properties / fixedCosts / description
      Previous value: -"Total fixed periodic operating costs ($)"New value: +"Total periodic fixed operating overhead costs in currency units (rent, salaries, software). Must be positive."
    • changedInput schema / properties / unitPrice / description
      Previous value: -"Selling price per unit ($)"New value: +"Selling price per individual product or service unit in currency units. Must be greater than unitVariableCost."
    • changedInput schema / properties / unitVariableCost / description
      Previous value: -"Variable cost incurred per unit ($)"New value: +"Direct variable cost incurred per unit produced or delivered in currency units. Must be non-negative."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it declares the operation deterministic, idempotent, and side-effect-free, and gives exact equations for each derived value. It also notes the return behavior ('Returns detailed breakdown'), so an agent knows what to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is organized into a terse summary, a behavior block, and a usage block with no wasted sentences. The core outputs are front-loaded, and formula details are compactly formatted.

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

Completeness5/5

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

Given a fully documented schema, no output schema, and no annotations, the description provides enough computational detail, optional-input behavior, and routing guidance for an agent to invoke the tool correctly. The formulas plus 'Returns detailed breakdown' are sufficient to predict the output.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds value by showing how parameters map into formulas (unitPrice - unitVariableCost, fixedCosts / CM) and by explaining the conditional role of expectedUnitsSold. This goes beyond the schema's field-level descriptions without needing to restate them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Calculate cost-volume-profit break-even thresholds...' and enumerates outputs (units, revenue, CM ratio, margin of safety, DOL). It further differentiates itself from billable_floor by explicitly naming the alternative.

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

Usage Guidelines5/5

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

Provides concrete use cases ('pricing strategy, manufacturing and SaaS unit economics, operational risk appraisal') and an explicit negative case with the correct alternative ('Do not use for hourly freelance billing rate minimums; use billable_floor instead').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TrueCalci toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a separate calculation formula or regulatory context, and descriptions include explicit 'do not use... use X instead' cross-references that clearly separate similar calculators. Even overlapping financial/loan/tax tools are disambiguated by geography, employment model, or specific formula.

Naming Consistency4/5

All tool names are lowercase snake_case and follow a domain/acronym-plus-descriptor pattern, making the set visually and structurally consistent. Minor outliers like casio_991_solve and heavy acronyms (npv_irr, scorp_optimizer) prevent it from being perfectly uniform.

Tool Count2/5

At 28 tools, the server is above the 25-tool threshold that makes broad tool scanning costly for an agent. Every calculator is distinct, but the mix of unrelated domains (tax, fluid mechanics, rocket equations, restaurant tips) means most agents will only ever need a small subset.

Completeness4/5

The set covers a wide range of self-contained calculation domains, from finance and tax to physics and everyday bills, with no obvious dead ends—each tool returns a complete result. Missing general-purpose utilities such as unit/currency conversion or descriptive statistics are notable gaps, but they are workaroundable and don't break the server's specialized calculator model.

Resources