Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_amazon_fba_fee_margin

Calculate Amazon FBA referral and fulfillment fees, net unit profit, margin, and ROI from price, COGS, weight, and storage inputs.

Instructions

Amazon FBA Fulfillment Fee & Net Profit Margin Calculator. Calculate exact Amazon Seller Central net unit profits after deducting category referral fees, FBA pick-and-pack fulfillment fees, and landed COGS. Discipline: ECOMMERCE. Governing mathematical model / formula: Net Profit = Retail Price - Landed COGS - Amazon Referral Fee - FBA Fulfillment Fee.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of net_unit_profit (Net Profit Per Unit), net_profit_margin_pct (Net Margin (%)), total_amazon_fees (Total Amazon Fees (Referral + FBA)), roi_on_cogs (Return on Investment (ROI on COGS)) using amazon_retail_price (Amazon Listing Price ($) in $), landed_unit_cogs (Landed Unit Cost (COGS) in $), item_shipping_weight_oz (Shipping Weight (Ounces) in oz), amazon_referral_pct (Amazon Referral Commission (%) in %), monthly_storage_per_unit (Estimated Monthly Storage Fee 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 'Amazon FBA Fulfillment Fee & Net Profit Margin 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): "amazon-fba-fee-margin"

    • category (string): "ecommerce"

    • name (string): "Amazon FBA Fulfillment Fee & Net Profit Margin Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.net_unit_profit (Net Profit Per Unit): Formatted display string (e.g. '$13.09 / unit')

      • metrics.net_profit_margin_pct (Net Margin (%)): Formatted display string (e.g. '43.6%')

      • metrics.total_amazon_fees (Total Amazon Fees (Referral + FBA)): Formatted display string (e.g. '$10.10')

      • metrics.roi_on_cogs (Return on Investment (ROI on COGS)): Formatted display string (e.g. '192.5%')

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

Input Schema

NameRequiredDescriptionDefault
landed_unit_cogsNoLanded Unit Cost (COGS) ($). Manufactured cost + freight into Amazon fulfillment center. Default: 6.8. Min: 0.25. Max: 500.
amazon_referral_pctNoAmazon Referral Commission (%) (%). Standard referral fee is 15% for most product categories. Default: 15. Min: 6. Max: 45.
amazon_retail_priceNoAmazon Listing Price ($) ($). Buy Box sales price on Amazon. Default: 29.99. Min: 1. Max: 1000.
item_shipping_weight_ozNoShipping Weight (Ounces) (oz). Unit weight including primary packaging. Default: 14. Min: 1. Max: 800.
monthly_storage_per_unitNoEstimated Monthly Storage Fee ($). FBA monthly cubic foot storage fee allocated per unit. Default: 0.35. Min: 0. Max: 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

With zero annotations, the description carries the full disclosure burden and does so: pure deterministic computation, machine floating-point precision, read-only, idempotent, stateless, no side effects, and out-of-bounds inputs returning a diagnostic error rather than throwing. That is exactly the behavioral context an agent needs for a calculator with no annotation coverage.

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?

Purpose and formula are front-loaded and the sectioned layout (usage, behavior, returns) is easy to scan. It is longer than strictly necessary — parameter lists are restated in the WHEN TO USE block and again in RETURNS — but no sentence is misleading or pure filler.

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?

No output schema exists, so the RETURNS section documenting status, formula, echoed inputs, and each computed metric (with display-string formats) is genuinely load-bearing. Combined with the validation and error-status behavior, an agent has everything needed to call and interpret the tool.

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% with per-parameter defaults and min/max already documented, so the baseline is 3. The description adds value by naming each input with its unit and mapping them into the outputs they drive (net_unit_profit, roi_on_cogs, etc.), though it does not add syntax or edge-case interpretation beyond 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?

States a specific verb-and-resource ('Amazon FBA Fulfillment Fee & Net Profit Margin Calculator') and spells out the governing formula: Net Profit = Retail Price - Landed COGS - Referral Fee - FBA Fulfillment Fee. It also names the discipline (ECOMMERCE) and the generic dispatcher sibling it should not be confused with, so an agent can distinguish it 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?

Explicit WHEN TO USE, WHEN NOT TO USE (no qualitative/unquantified reasoning, all inputs must be numeric), and SIBLING ROUTING pointing to omni_universal_query for cross-discipline dispatch. The exclusions are somewhat boilerplate but the routing condition is concrete.

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