Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_cpa_cpc

Calculate cost per acquisition from average cost per click and landing page conversion rate, plus total conversions, campaign spend, and clicks per conversion for exact ad ROI analysis.

Instructions

Cost Per Acquisition (CPA) from CPC Calculator. Calculate Cost Per Acquisition (CPA) from Cost Per Click (CPC) and Landing Page Conversion Rate (CVR). Discipline: FINANCE. Governing mathematical model / formula: CPA = Cost Per Click (CPC) / Conversion Rate %.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of cpa_result (Cost Per Acquisition (CPA)), total_conversions (Total Conversions Driven), total_campaign_cost (Total Campaign Ad Spend), clicks_per_conversion (Clicks Needed per Conversion) using cpc_input (Average Cost Per Click (CPC)), conversion_rate_pct (Landing Page Conversion Rate in %), clicks_count (Traffic Volume (Clicks)). 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.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Cost Per Acquisition (CPA) from CPC Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

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): "cpa-cpc"

    • category (string): "finance"

    • name (string): "Cost Per Acquisition (CPA) from CPC Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.cpa_result (Cost Per Acquisition (CPA)): Formatted display string (e.g. '$78.57')

      • metrics.total_conversions (Total Conversions Driven): Formatted display string (e.g. '175 conversions')

      • metrics.total_campaign_cost (Total Campaign Ad Spend): Formatted display string (e.g. '$13,750.00')

      • metrics.clicks_per_conversion (Clicks Needed per Conversion): Formatted display string (e.g. '29 clicks')

    • 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_cpa_cpc"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpc_inputNoAverage Cost Per Click (CPC). Average Google/Meta cost per click. Default: 2.75. Min: 0.05. Max: 100.
clicks_countNoTraffic Volume (Clicks). Total paid click volume. Default: 5000. Min: 50. Max: 1000000.
conversion_rate_pctNoLanding Page Conversion Rate (%). Percentage of visitors who convert into leads/buyers. Default: 3.5. Min: 0.1. Max: 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/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 full burden and does so: deterministic floating-point computation, read-only, idempotent, stateless, zero side effects, plus the specific failure mode that out-of-bounds input returns a diagnostic error status instead of throwing. It also documents the response envelope (status, calculator, category, formula, echoed inputs, metrics, execution_time_ms).

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?

Headers are front-loaded (purpose and formula first, returns last) and the RETURNS section is justified because no output schema exists. There is mild duplication in repeating each parameter's human label immediately after its machine name, and the example formatted strings are somewhat padded, but nothing is off-topic.

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?

With zero annotations and no output schema, the description must cover safety, validation behavior and return shape — and it does all three. For a three-parameter deterministic calculator, an agent has everything needed to call it correctly and interpret the response.

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 already 100%, with labels, defaults and min/max bounds on all three parameters, so the description's restatement of cpc_input, conversion_rate_pct and clicks_count adds little new semantics. It does helpfully link those inputs to the derived metrics (e.g. clicks driving total_campaign_cost and total_conversions), but that linkage is implicit rather than spelled out.

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?

States a specific verb and resource ('Calculate Cost Per Acquisition (CPA) from Cost Per Click (CPC) and Landing Page Conversion Rate') and gives the governing formula CPA = CPC / CVR. It also names the generic dispatcher omni_universal_query as the thing it is not, so an agent can separate it from siblings without opening a 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?

The 'WHEN TO USE' block enumerates the exact inputs and outputs covered, the 'WHEN NOT TO USE' block excludes qualitative or non-numeric work, and the disambiguation section routes chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver. Both the positive condition and the alternatives are explicit.

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