Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_crypto_payment_processor_fees

Calculate annual payment processing savings, chargeback elimination, and settlement fees by comparing crypto gateway costs with credit card interchange fees.

Instructions

Crypto Payment Gateway vs Credit Card Interchange Processing Fees. Calculate annual payment processing dollar savings, chargeback elimination, and settlement fees when accepting crypto (1% flat) vs credit cards (2.9% + $0.30). Discipline: CRYPTO. Governing mathematical model / formula: Annual Savings = (Credit Card Fees + Chargebacks) - Crypto Gateway Fees.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of annual_merchant_savings (Annual Processing Savings), net_fee_reduction_pct (Payment Processing Cost Reduction), credit_card_total_fees (Total Credit Card Fees + Fraud), crypto_processing_cost (Total Crypto Processing Cost) using annual_merchant_sales (Annual Merchant Sales ($ USD)), average_order_value_usd (Average Order Value ($ AOV)), cc_interchange_rate_pct (Credit Card Processing Fee (%) in %), crypto_gateway_fee_pct (Crypto Processor Fee (%) in %), chargeback_loss_pct (Credit Card Chargeback Fraud 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Crypto Payment Gateway vs Credit Card Interchange Processing Fees' 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): "crypto-payment-processor-fees"

    • category (string): "crypto"

    • name (string): "Crypto Payment Gateway vs Credit Card Interchange Processing Fees"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.annual_merchant_savings (Annual Processing Savings): Formatted display string (e.g. '$19,650.00 / yr')

      • metrics.net_fee_reduction_pct (Payment Processing Cost Reduction): Formatted display string (e.g. '71.5% Fee Cut')

      • metrics.credit_card_total_fees (Total Credit Card Fees + Fraud): Formatted display string (e.g. '$27,150.00 / yr')

      • metrics.crypto_processing_cost (Total Crypto Processing Cost): Formatted display string (e.g. '$7,500.00 / yr')

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

Input Schema

NameRequiredDescriptionDefault
chargeback_loss_pctNoCredit Card Chargeback Fraud Rate (%) (%). Lost revenue from credit card friendly fraud and chargebacks. Default: 0.75. Min: 0. Max: 3.
annual_merchant_salesNoAnnual Merchant Sales ($ USD). Total annual e-commerce or B2B sales volume. Default: 750000. Min: 25000. Max: 50000000.
crypto_gateway_fee_pctNoCrypto Processor Fee (%) (%). BitPay, Coinbase Commerce, or NOWPayments (typically 0.5% - 1.0%). Default: 1. Min: 0.1. Max: 2.5.
average_order_value_usdNoAverage Order Value ($ AOV). Mean checkout dollar amount. Default: 85. Min: 5. Max: 5000.
cc_interchange_rate_pctNoCredit Card Processing Fee (%) (%). Stripe/PayPal standard = 2.9% + $0.30. Default: 2.9. Min: 1.5. Max: 4.5.

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 full behavioral burden and does so thoroughly: it declares read-only, idempotent, stateless operation with zero side effects, input validation against bounds, and safe diagnostic errors instead of runtime exceptions. This gives the agent enough confidence to invoke the tool correctly.

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 description is well organized with clear sections for purpose, formula, usage, behavior, and returns, and the core purpose is front-loaded. It is somewhat verbose and repeats some schema-level parameter detail, but the extra structure supports correct invocation of a multi-input calculator.

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 five-parameter deterministic calculator with no output schema, the description is complete: it explains the formula, input validation behavior, error semantics, and the exact shape of the returned metrics. An agent has all the information needed to call the tool and interpret its result.

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 the input schema already documents each parameter with defaults, bounds, and business meaning. The description reinforces parameter names and uses them in the calculation context, but adds little semantic detail beyond what the schema already provides, which is the baseline expectation.

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 states a specific calculation domain: comparing crypto payment gateway fees against credit card interchange fees to compute annual merchant savings, chargeback elimination, and settlement costs. It explicitly distinguishes this dedicated specialist calculator from generic dispatchers such as omni_universal_query.

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 provides explicit WHEN TO USE and WHEN NOT TO USE sections, lists the deterministic outputs and required inputs, and routes the agent away from generic dispatchers. The conditions for using this calculator versus alternatives are clear and actionable.

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