Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_economic_order_quantity_eoq

Calculate optimal order quantity, annual order frequency, and minimum inventory holding cost from demand and cost inputs to eliminate manual arithmetic errors.

Instructions

Economic Order Quantity (EOQ) & Annual Holding Cost Calculator. Calculate optimal purchasing batch size (EOQ), annual ordering frequency, and minimized total inventory holding costs (Ford W. Harris formula). Discipline: LOGISTICS. Governing mathematical model / formula: EOQ = √[(2 · Annual Demand · Order Cost) / Annual Holding Cost per Unit].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of optimal_eoq_units (Economic Order Quantity (EOQ)), annual_orders_count (Optimal Orders Per Year), min_total_inventory_cost (Total Annual Inventory Cost), cycle_inventory_days (Days of Supply Per Order) using annual_unit_demand (Annual Demand (Units/Year) in units/yr), order_setup_cost (Fixed Cost per Purchase Order ($)), unit_purchase_cost (Unit Item Cost ($)), holding_cost_rate_pct (Annual Carrying Cost Rate (%) 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 'Economic Order Quantity (EOQ) & Annual Holding Cost 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): "economic-order-quantity-eoq"

    • category (string): "logistics"

    • name (string): "Economic Order Quantity (EOQ) & Annual Holding Cost Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.optimal_eoq_units (Economic Order Quantity (EOQ)): Formatted display string (e.g. '447 Units')

      • metrics.annual_orders_count (Optimal Orders Per Year): Formatted display string (e.g. '26.8 Orders / Year')

      • metrics.min_total_inventory_cost (Total Annual Inventory Cost): Formatted display string (e.g. '$4,025.00 / yr')

      • metrics.cycle_inventory_days (Days of Supply Per Order): Formatted display string (e.g. '13.6 Days')

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

Input Schema

NameRequiredDescriptionDefault
order_setup_costNoFixed Cost per Purchase Order ($). Labor, PO processing, customs documentation, receiving fee. Default: 75. Min: 5. Max: 1000.
annual_unit_demandNoAnnual Demand (Units/Year) (units/yr). Total annual sales demand in units. Default: 12000. Min: 100. Max: 1000000.
unit_purchase_costNoUnit Item Cost ($). Cost of goods purchased from manufacturer. Default: 45. Min: 1. Max: 5000.
holding_cost_rate_pctNoAnnual Carrying Cost Rate (%) (%). Warehousing, insurance, capital cost, obsolescence (typically 18-25%). Default: 20. Min: 5. Max: 40.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

No annotations provided, yet the description discloses deterministic floating-point computation, read-only/idempotent/stateless behavior, no side effects, and bounded-input validation returning a safe error status instead of throwing.

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?

Good sectioning and front-loading, but bloated by duplicated verbose parenthetical labels in both the input and metric lists that add length without information.

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, the RETURNS section usefully enumerates status, calculator, echoed inputs, and each metric with example formats; only precision/rounding of the formatted strings is left unstated.

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 coverage is 100% and the schema already documents units, defaults, and ranges; the description restates the same parameter meanings without adding relationships or edge-case semantics, so the baseline of 3 applies.

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?

Specific verb+resource (compute EOQ, ordering frequency, holding cost) with the exact governing formula stated, distinguishing it from sibling numeric and dispatcher 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, WHEN NOT TO USE, and disambiguation naming omni_universal_query, omni_batch_calculate, and 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