Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_retail_markdown_optimization

Calculate optimal clearance discount tiers to clear slow-moving inventory and compare total cash recovered against preserved gross margin.

Instructions

Retail Markdown & Clearance Discount Optimization Calculator. Calculate optimal discount tiers to clear slow-moving inventory, comparing total cash recovered against preserved gross margin. Discipline: ECOMMERCE. Governing mathematical model / formula: Clearance Price = Original Price × (1 - Markdown %) | Cash Recovered = Inventory Units × Clearance Price.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of discounted_clearance_price (Clearance Selling Price), total_cash_liquidation_value (Total Cash Liquidated), remaining_profit_per_unit (Net Profit Preserved Above Cost), markdown_margin_pct (Preserved Gross Margin (%)) using original_retail_price (Original Retail Ticket Price in $), inventory_unit_cogs (Unit Inventory Cost (COGS) in $), slow_moving_units_on_hand (Slow-Moving Units on Hand in units), proposed_markdown_pct (Proposed Markdown Discount (%) 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Retail Markdown & Clearance Discount Optimization 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): "retail-markdown-optimization"

    • category (string): "ecommerce"

    • name (string): "Retail Markdown & Clearance Discount Optimization Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.discounted_clearance_price (Clearance Selling Price): Formatted display string (e.g. '$57.85 / unit')

      • metrics.total_cash_liquidation_value (Total Cash Liquidated): Formatted display string (e.g. '$49,173 Total')

      • metrics.remaining_profit_per_unit (Net Profit Preserved Above Cost): Formatted display string (e.g. '+$31.85 / unit')

      • metrics.markdown_margin_pct (Preserved Gross Margin (%)): Formatted display string (e.g. '55.1%')

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

Input Schema

NameRequiredDescriptionDefault
inventory_unit_cogsNoUnit Inventory Cost (COGS) ($). Cost of goods on balance sheet. Default: 26. Min: 2. Max: 500.
original_retail_priceNoOriginal Retail Ticket Price ($). Standard non-discounted MSRP. Default: 89. Min: 10. Max: 1000.
proposed_markdown_pctNoProposed Markdown Discount (%) (%). Percentage off original MSRP. Default: 35. Min: 5. Max: 85.
slow_moving_units_on_handNoSlow-Moving Units on Hand (units). Quantity slated for clearance liquidation. Default: 850. Min: 10. Max: 100000.

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?

With no annotations supplied, the description carries the whole burden and does: read-only, idempotent, stateless, zero side effects, deterministic floating-point precision, and bounds validation that returns a diagnostic error rather than throwing. It also flags the precision guarantee against LLM arithmetic error, which is genuinely useful behavioral context.

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?

Headings (USAGE GUIDELINES, BEHAVIOR & SAFETY, RETURNS) front-load the key routing and behavior, and the formula appears early. It runs long, and the parameter enumeration inside WHEN TO USE largely restates schema fields, costing some efficiency.

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?

There is no output schema, but the RETURNS block fully specifies the response shape including status, calculator, inputs echo, and each metrics field with example formatting. Combined with validation behavior and defaults, an agent has everything needed to call and interpret this tool.

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% and already documents units, defaults, and min/max for all four parameters, so the baseline is 3. The description does connect each parameter to its output metric (e.g. inventory_unit_cogs → remaining_profit_per_unit), which adds modest interpretive value but does not exceed what the schema states.

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 optimal discount tiers to clear slow-moving inventory') plus the governing formula (Clearance Price = Original Price × (1 - Markdown %)), and names itself as a dedicated specialist distinct from omni_universal_query. An agent can identify what it 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?

The definition has explicit WHEN TO USE, WHEN NOT TO USE ('not for qualitative evaluations or unquantified reasoning; all inputs must be numeric'), and SIBLING ROUTING to omni_universal_query for cross-discipline dispatch. 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