Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_aov_expansion_elasticity

Calculates AOV expansion and cross-sell uplift, including expanded average order value, AOV lift, and incremental monthly and annual revenue from attach rates and order bumps.

Instructions

Average Order Value (AOV) Expansion & Cross-Sell Uplift Calculator. Calculate incremental top-line and annual revenue generated by increasing post-purchase cross-sell attach rates and order bumping. Discipline: ECOMMERCE. Governing mathematical model / formula: New AOV = Baseline AOV + (Attach Rate % × Add-On Price) | Monthly Uplift = Monthly Orders × (New AOV - Baseline AOV).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of expanded_store_aov (Expanded Average Order Value), aov_dollar_increase (Average AOV Lift Per Order), monthly_incremental_revenue (Monthly Incremental Revenue), annual_revenue_expansion (Annualized Top-Line Gain) using monthly_order_volume (Monthly Order Volume in orders), baseline_store_aov (Current Baseline AOV in $), cross_sell_attach_rate_pct (Cross-Sell / Order Bump Attach Rate (%) in %), cross_sell_item_price (Add-On Cross-Sell Retail Price in $). 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 'Average Order Value (AOV) Expansion & Cross-Sell Uplift 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): "aov-expansion-elasticity"

    • category (string): "ecommerce"

    • name (string): "Average Order Value (AOV) Expansion & Cross-Sell Uplift Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.expanded_store_aov (Expanded Average Order Value): Formatted display string (e.g. '$65.96 / order')

      • metrics.aov_dollar_increase (Average AOV Lift Per Order): Formatted display string (e.g. '+$3.96 / order')

      • metrics.monthly_incremental_revenue (Monthly Incremental Revenue): Formatted display string (e.g. '$15,840 / mo')

      • metrics.annual_revenue_expansion (Annualized Top-Line Gain): Formatted display string (e.g. '$190,080 / year')

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

Input Schema

NameRequiredDescriptionDefault
baseline_store_aovNoCurrent Baseline AOV ($). Average ticket price before cross-sell optimization. Default: 62. Min: 10. Max: 1000.
monthly_order_volumeNoMonthly Order Volume (orders). Total orders transacted each month. Default: 4000. Min: 100. Max: 500000.
cross_sell_item_priceNoAdd-On Cross-Sell Retail Price ($). Selling price of the recommended complementary product. Default: 22. Min: 3. Max: 200.
cross_sell_attach_rate_pctNoCross-Sell / Order Bump Attach Rate (%) (%). Percentage of buyers who accept the checkout add-on. Default: 18. Min: 2. Max: 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discharges most of it: deterministic floating-point computation, read-only/idempotent/stateless, and bounded input validation returning a diagnostic error status rather than throwing. It also documents the full return envelope including status, metric formatting, and latency. Precision is not fully specified (formatting is display strings, so numeric precision of the underlying float is left implicit).

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?

Sectioned and front-loaded with the formula before any detail, so an agent can stop reading early if it just wants the compute call. There is measurable redundancy: the parameter list in USAGE GUIDELINES replays schema descriptions nearly verbatim, and it sits before the more decision-relevant DISAMBIGUATION block.

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

Completeness4/5

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

With no output schema and no annotations, the description has to cover both the contract and the behavior, and it does: formula, metric-by-metric return fields with sample formats, error semantics, and sibling routing. The remaining gap is quantitative precision, since the computed metrics are advertised as formatted display strings with no raw numeric field documented.

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% and each parameter already documents units, defaults, and min/max, so the baseline would be 3. The description adds a small amount by restating each parameter with its business meaning (attach rate = percentage of buyers who accept the add-on) and by giving the formula that binds them together, which clarifies how the four inputs interact. That is marginally above the schema.

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 verb+resource (AOV Expansion & Cross-Sell Uplift Calculator) plus the governing formula, and states the discipline (ECOMMERCE), which cleanly separates it from the generic dispatcher and the batch tool. An agent can identify the exact calculation and its two-step math 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 provides an explicit WHEN TO USE with the full output set, a WHEN NOT TO USE clause (no qualitative reasoning, numeric inputs only), and disambiguation routing to omni_universal_query, omni_batch_calculate, and omni_describe_solver. The alternatives and the conditions that select them are stated outright rather than inferred.

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