Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_inventory_bullwhip_effect

Calculate supply chain bullwhip effect by comparing order and demand variance across echelons, returning amplification ratio, upstream order variance, excess inventory cost, and instability severity.

Instructions

Supply Chain Bullwhip Effect Variance Amplification Calculator. Calculate order variance amplification ratio across supply chain echelons (retailer, distributor, manufacturer) to measure the Bullwhip Effect. Discipline: LOGISTICS. Governing mathematical model / formula: Bullwhip Measure = (Variance of Orders / Mean of Orders) / (Variance of Demand / Mean of Demand).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of bullwhip_amplification_ratio (Bullwhip Amplification Multiplier), upstream_order_variance (Upstream Factory Order Variance), excess_inventory_cost_pct (Estimated Excess Safety Stock Penalty), distortion_severity (Supply Chain Instability Tier) using retail_demand_variance (Consumer Demand Variance (σ²_demand)), lead_time_echelons (Cumulative Supply Chain Lead Time (Days) in days), forecasting_factor (Demand Forecasting Smoothing (p)). 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 'Supply Chain Bullwhip Effect Variance Amplification 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): "inventory-bullwhip-effect"

    • category (string): "logistics"

    • name (string): "Supply Chain Bullwhip Effect Variance Amplification Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.bullwhip_amplification_ratio (Bullwhip Amplification Multiplier): Formatted display string (e.g. '3.85x')

      • metrics.upstream_order_variance (Upstream Factory Order Variance): Formatted display string (e.g. '173.2 (vs 45.0 Retail)')

      • metrics.excess_inventory_cost_pct (Estimated Excess Safety Stock Penalty): Formatted display string (e.g. '+48.0% Working Capital Waste')

      • metrics.distortion_severity (Supply Chain Instability Tier): Formatted display string (e.g. 'High Distortion (VMI Recommended)')

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

Input Schema

NameRequiredDescriptionDefault
forecasting_factorNoDemand Forecasting Smoothing (p). Order update smoothing factor (Chen et al. model). Default: 0.25. Min: 0.05. Max: 0.95.
lead_time_echelonsNoCumulative Supply Chain Lead Time (Days) (days). Total lead time across ordering tiers. Default: 28. Min: 2. Max: 180.
retail_demand_varianceNoConsumer Demand Variance (σ²_demand). Variance of point-of-sale customer purchases. Default: 45. Min: 5. Max: 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares pure deterministic computation, read-only/idempotent/stateless semantics with zero side effects, bounded input validation, and safe diagnostic errors instead of exceptions. It also lists the exact return payload, which removes ambiguity about post-call state.

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 sectioned layout (usage, boundaries, safety, returns) is easy to scan and front-loads the purpose, but there is meaningful redundancy: metric names and their parenthetical descriptions appear once in WHEN TO USE and again in RETURNS, and the title is repeated verbatim. It is longer than the calculation warrants.

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?

For a three-parameter deterministic calculator with no output schema, the definition covers everything an agent needs: the formula, bounded inputs with defaults, error behavior, and a field-by-field description of the returned JSON including formatted metric strings and execution time.

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 100%, so units, defaults, and min/max for all three parameters are already fully documented in the schema. The description restates parameter labels and units in the usage section but adds no new interpretation, keeping this at the baseline for high-coverage schemas.

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+resource ('Calculate order variance amplification ratio across supply chain echelons') and names the governing formula, so an agent knows exactly what computation is performed. It is clearly distinguishable from generic siblings like omni_universal_query and from other inventory tools.

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?

Explicit WHEN TO USE (deterministic ratio/variance/severity calculation with listed inputs) and WHEN NOT TO USE (qualitative reasoning, non-numeric inputs) sections are provided. Disambiguation further routes chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver.

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