Skip to main content
Glama

Saura: Saudi Business Calculators

Saudi payment gateway fee comparison

compare_payment_gateway_fees
Read-onlyIdempotent

Compares the monthly and first-year fees of payment gateways in Saudi Arabia for a store's sales and payment mix (mada, Visa/Mastercard, STC Pay). Built-in published price lists: Amazon Payment Services standard plan (aps) and Paymes by PayTabs (paymes); Tap (tap) and up to two other gateways (Moyasar, HyperPay, Geidea, PayTabs, Checkout.com or other) are priced from a quote you supply. Returns each option's fees before and with 15% VAT, the effective rate, the cheapest option and the yearly saving (names and tips in Arabic).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monthly_sales": "<monthly_sales>",
      "monthly_orders": "<monthly_orders>",
      "mada_pct": "<mada_pct>",
      "card_pct": "<card_pct>"
    },
    "name": "compare_payment_gateway_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
plansNoGateways with built-in prices to include. tap needs tap_card_pct when any card or STC Pay share is above 0
quotesNoUp to two written quotes from other gateways
card_pctYesShare paid with Visa / Mastercard, %
mada_pctYesShare of sales paid with mada, %
stc_pay_pctNoShare paid with STC Pay, %. mada_pct + card_pct + stc_pay_pct must equal 100
tap_monthlyNoTap quote: monthly fee, SAR
tap_card_pctNoTap quote: card fee %
monthly_salesYesMonthly card and wallet sales in SAR
monthly_ordersYesPaid orders per month
tap_card_fixedNoTap quote: fixed fee per card payment, SAR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond them: the provenance of the pricing data (published price lists vs. user-supplied quotes) and the VAT treatment applied (15%). It does not discuss edge cases such as what happens if the payment shares do not sum to 100.

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?

Front-loaded with the verb and resource, then moves to data sources and outputs in a logical order with no filler sentences. The parenthetical gateway enumerations are dense but each name is load-bearing for the pricing model, so little could be cut without losing information.

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?

With 10 parameters and no output schema, the description carries the return-value burden itself and does so: fees before and with VAT, effective rate, cheapest option, and yearly saving. Combined with 100% schema coverage, an agent has everything needed to call it and interpret the result.

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%, so the baseline is 3, but the description adds genuine semantics: it clarifies that 'plans' selects gateways with built-in price lists while 'quotes' carries written quotes from other providers, and it flags that tap is listed as a plan yet still needs tap_card_pct. That resolves a real ambiguity an agent would otherwise hit in 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 (compares) and resource (payment gateway fees in Saudi Arabia) and scopes it to a store's sales and payment mix (mada, Visa/Mastercard, STC Pay). It also enumerates which gateways are priced from built-in lists versus supplied quotes, so it is clearly distinguishable from siblings like calculate_saudi_vat or compare_salla_zid_costs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: 'aps' and 'paymes' come with built-in prices, while 'tap' and up to two other gateways must be priced from a quote the caller supplies. It does not name a when-not condition or point to an alternative tool, but the scope is narrow enough that the usage boundary is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources