Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_cac

Calculate blended and paid Customer Acquisition Cost by dividing total sales and marketing spend by new customers, returning exact per-customer marketing and sales shares.

Instructions

Customer Acquisition Cost (CAC) Calculator. Calculate blended and paid Customer Acquisition Cost (CAC) from total sales and marketing expenditure divided by new acquired customers. Discipline: FINANCE. Governing mathematical model / formula: CAC = Total Sales & Marketing Spend / Number of New Customers Acquired.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of blended_cac (Blended Customer Acquisition Cost), total_acquisition_spend (Total S&M Expenditure), marketing_cac_share (Marketing Share per Customer), sales_cac_share (Sales Share per Customer) using marketing_spend (Total Marketing & Ad Spend), sales_spend (Sales Salaries & Commissions), new_customers (New Customers Acquired). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Customer Acquisition Cost (CAC) Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "cac"

    • category (string): "finance"

    • name (string): "Customer Acquisition Cost (CAC) Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.blended_cac (Blended Customer Acquisition Cost): Formatted display string (e.g. '$500.00')

      • metrics.total_acquisition_spend (Total S&M Expenditure): Formatted display string (e.g. '$60,000.00')

      • metrics.marketing_cac_share (Marketing Share per Customer): Formatted display string (e.g. '$208.33')

      • metrics.sales_cac_share (Sales Share per Customer): Formatted display string (e.g. '$291.67')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_cac"
  }
}

Input Schema

NameRequiredDescriptionDefault
sales_spendNoSales Salaries & Commissions. SDR/AE salaries, bonuses, and commission payouts. Default: 35000. Min: 500. Max: 2000000.
new_customersNoNew Customers Acquired. Total new paying customers in the measurement window. Default: 120. Min: 1. Max: 50000.
marketing_spendNoTotal Marketing & Ad Spend. Paid advertising, software, agency, and creative fees. Default: 25000. Min: 500. Max: 2000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the entire burden, and it does: it declares pure deterministic computation, read-only, idempotent, stateless, zero side effects, bounds-validated inputs, and that out-of-bounds inputs return a diagnostic error status rather than throwing. That is exactly the behavioral profile an agent needs before invoking a calculator.

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?

The purpose and usage sections are front-loaded and well-sectioned, but the RETURNS block is verbose boilerplate that enumerates every static envelope field (calculator, category, name, formula, execution_time_ms) with example strings. Substantial trimming is possible without losing information the agent needs.

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?

Although there is no output schema, the RETURNS section documents the full response envelope including status values, echoed inputs, and each computed metric. Combined with the validation and error-handling notes, nothing an agent needs to call this correctly or interpret its result is missing.

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, but the description adds value by tying each parameter to its role in the formula and to the resulting metric (marketing_spend and sales_spend split into marketing_cac_share and sales_cac_share). It does not add units or window conventions beyond what the schema already states, keeping it out of the top band.

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 names a specific resource (Customer Acquisition Cost Calculator) and states the exact formula CAC = Total S&M Spend / New Customers Acquired. It also distinguishes related outputs (blended vs. paid components via marketing_cac_share and sales_cac_share), so an agent knows precisely what this computes without opening the schema.

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?

It gives explicit WHEN TO USE conditions listing the exact parameters and outputs, a WHEN NOT TO USE clause excluding qualitative reasoning and non-numeric inputs, and a SIBLING ROUTING note pointing generic dispatch to omni_universal_query. This is the full when/when-not/alternative triad.

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

Deploy Server

Other Tools