Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_margin_markup

Converts between gross profit margin and markup percentage, calculates target selling prices, and eliminates pricing confusion for accurate financial analysis.

Instructions

Margin vs Markup Multiplier Calculator. Convert between Gross Profit Margin and Markup percentage, calculate target selling prices, and eliminate pricing confusion. Discipline: FINANCE. Governing mathematical model / formula: Margin % = Markup / (1 + Markup) vs Markup % = Margin / (1 - Margin).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of gross_margin_pct (Gross Profit Margin), markup_pct (Markup on Cost), gross_profit_dollars (Gross Profit ($)) using item_cost (Cost of Goods Sold (COGS)), selling_price (Selling Price to Customer). 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 'Margin vs Markup Multiplier 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): "margin-markup"

    • category (string): "finance"

    • name (string): "Margin vs Markup Multiplier Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.gross_margin_pct (Gross Profit Margin): Formatted display string (e.g. '36.00%')

      • metrics.markup_pct (Markup on Cost): Formatted display string (e.g. '56.25%')

      • metrics.gross_profit_dollars (Gross Profit ($)): Formatted display string (e.g. '$45.00')

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

Input Schema

NameRequiredDescriptionDefault
item_costNoCost of Goods Sold (COGS). Wholesale or manufacturing cost. Default: 80. Min: 1. Max: 50000.
selling_priceNoSelling Price to Customer. Retail sales price. Default: 125. Min: 1. Max: 100000.

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?

With no annotations supplied, the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless with zero side effects, and describes validation behavior (out-of-bounds inputs return a diagnostic error status without throwing). Determinism and floating-point precision are stated up front. This is well beyond what a bare schema would convey.

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?

The header line and formulas are front-loaded, and the labeled sections (usage, behavior, returns) make scanning easy. It is somewhat long and repeats the tool's display name and category in the returns block, but each section carries information an agent needs given the absence of an output schema.

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 two-input deterministic calculator with no output schema, the description fully spells out the response envelope – status, calculator, category, formula, echoed inputs, per-metric display strings, and execution time. An agent can parse results and handle the error case without further information.

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 both parameters already document defaults (80, 125), bounds, and domain meaning, so the schema does the heavy lifting. The description restates the domain framing (COGS vs retail price) but adds no new syntax, interaction, or edge-case guidance for the two inputs. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Margin vs Markup Multiplier Calculator) and states the concrete operations: converting between gross margin and markup, and computing selling prices. It even supplies the governing formulas, so the agent knows exactly what is being computed. The minor flaw is the phrase 'calculate target selling prices', which overstates scope – the tool only derives margin/markup from cost and price inputs.

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 has an explicit WHEN TO USE list mapping inputs (item_cost, selling_price) to outputs, an explicit WHEN NOT TO USE exclusion for qualitative reasoning, and a SIBLING ROUTING line naming omni_universal_query as the generic alternative. That 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