Skip to main content
Glama

My effective rate

my_effective_rate

What the owner really pays to get paid, from their own exports, next to the published fee for the same payments and the cheapest route their payers can use, with the yearly saving in dollars. Send totals only, one row per route and period: {route, period_start, period_end, gross_volume, fees_paid, payment_count}. Never send customer names, emails or transaction ids; PaidRouter stores only these totals. Stripe: export the itemized Payout reconciliation report (Reports → Payout reconciliation) or Balance → Balance change from activity, itemized, and add the payment_method_type column. Keep rows with reporting_category = charge. Card rows go to stripe_card (stripe_terminal if taken in person), us_bank_account rows to stripe_ach. Per route, send the sum of gross, the sum of fee and the number of rows, with the first and last created date as the period. Amounts are in dollars. The plain Payouts list export has no per-payment fees; don't use it. PayPal: Activity → Reports → Activity download, CSV. Keep completed payments received: Status = Completed, positive Gross, Type such as Express Checkout Payment, Website Payment, General Payment or Mobile Payment. Checkout payments go to paypal_checkout (paypal_card if you can tell they were guest card payments), goods-and-services payments from PayPal users go to paypal_gs. Send the sum of Gross, the sum of Fee (PayPal may show it as a negative number; either sign works), and the row count, with the first and last Date as the period.

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": {
      "totals": "<totals>"
    },
    "name": "my_effective_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
totalsYes
payer_pays_byNoHow the owner's payers could pay instead. Default: the same way as today (card stays card). 'any' also counts bank transfer, which needs the payer's agreement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / totals / items / properties / route / enum
      Previous value: -[
      -  "quickbooks_payments_invoice_card",
      -  "quickbooks_payments_desktop_invoice_card",
      -  "freshbooks_invoice_card",
      -  "wave_invoice_card",
      -  "xero_invoice_card",
      -  "zoho_payments_card_online",
      -  "bill_com_invoice_card",
      -  "honeybook_invoice_card",
      -  "bonsai_invoice_card",
      -  "housecall_pro_invoice_card",
      -  "godaddy_payments_card_online",
      -  "godaddy_payments_invoice_card",
      -  "wix_payments_card_online",
      -  "squarespace_payments_card_online",
      -  "squarespace_payments_card_online_plus",
      -  "squarespace_payments_card_online_advanced",
      -  "square_card_online",
      -  "square_card_online_square_premium",
      -  "sumup_invoice_card",
      -  "paypal_invoice_card",
      -  "airwallex_card_online",
      -  "squarespace_payments_card_online_core",
      -  "square_card_online_square_plus",
      -  "stripe_card",
      -  "square_card",
      -  "paypal_checkout",
      -  "paypal_card",
      -  "helcim_card",
      -  "melio_card",
      -  "shopify_card",
      -  "quickbooks_payments_card_in_person",
      -  "xero_card_in_person",
      -  "jobber_card_in_person",
      -  "housecall_pro_card_in_person",
      -  "clover_card_in_person_retail_growth",
      -  "godaddy_payments_card_in_person",
      -  "wix_payments_card_in_person",
      -  "wix_payments_tap_to_pay",
      -  "squarespace_payments_card_in_person",
      -  "shopify_payments_card_in_person",
      -  "shopify_payments_card_in_person_grow",
      -  "shopify_payments_card_in_person_advanced",
      -  "shopify_payments_card_in_person_plus",
      -  "square_card_in_person_square_plus",
      -  "square_card_in_person_square_premium",
      -  "lightspeed_card_in_person",
      -  "sumup_card_in_person",
      -  "paypal_pos_card_in_person",
      -  "stripe_tap_to_pay",
      -  "squarespace_payments_card_in_person_core",
      -  "stripe_terminal",
      -  "square_in_person",
      -  "helcim_in_person",
      -  "quickbooks_payments_invoice_ach",
      -  "freshbooks_invoice_ach",
      -  "wave_invoice_ach",
      -  "xero_invoice_ach",
      -  "xero_bank_transfer",
      -  "gocardless_ach_debit",
      -  "zoho_payments_ach_debit",
      -  "bill_com_invoice_ach",
      -  "honeybook_invoice_ach",
      -  "bonsai_invoice_ach",
      -  "jobber_invoice_ach",
      -  "housecall_pro_invoice_ach",
      -  "melio_ach",
      -  "stripe_ach",
      -  "helcim_ach",
      -  "square_ach",
      -  "paypal_ach",
      -  "zelle_business",
      -  "wise_business_bank",
      -  "payoneer_bank",
      -  "venmo_business",
      -  "cash_app_business",
      -  "paypal_gs"
      -]New value: +[
      +  "quickbooks_payments_invoice_card",
      +  "quickbooks_payments_desktop_invoice_card",
      +  "freshbooks_invoice_card",
      +  "wave_invoice_card",
      +  "xero_invoice_card",
      +  "zoho_payments_card_online",
      +  "bill_com_invoice_card",
      +  "honeybook_invoice_card",
      +  "bonsai_invoice_card",
      +  "housecall_pro_invoice_card",
      +  "godaddy_payments_card_online",
      +  "godaddy_payments_invoice_card",
      +  "wix_payments_card_online",
      +  "squarespace_payments_card_online",
      +  "squarespace_payments_card_online_plus",
      +  "squarespace_payments_card_online_advanced",
      +  "square_card_online",
      +  "square_card_online_square_premium",
      +  "sumup_invoice_card",
      +  "paypal_invoice_card",
      +  "airwallex_card_online",
      +  "stripe_card",
      +  "square_card",
      +  "paypal_checkout",
      +  "paypal_card",
      +  "helcim_card",
      +  "melio_card",
      +  "shopify_card",
      +  "quickbooks_payments_card_in_person",
      +  "xero_card_in_person",
      +  "jobber_card_in_person",
      +  "housecall_pro_card_in_person",
      +  "clover_card_in_person_retail_growth",
      +  "godaddy_payments_card_in_person",
      +  "wix_payments_card_in_person",
      +  "wix_payments_tap_to_pay",
      +  "squarespace_payments_card_in_person",
      +  "shopify_payments_card_in_person",
      +  "shopify_payments_card_in_person_grow",
      +  "shopify_payments_card_in_person_advanced",
      +  "shopify_payments_card_in_person_plus",
      +  "square_card_in_person_square_plus",
      +  "square_card_in_person_square_premium",
      +  "lightspeed_card_in_person",
      +  "sumup_card_in_person",
      +  "paypal_pos_card_in_person",
      +  "stripe_tap_to_pay",
      +  "stripe_terminal",
      +  "square_in_person",
      +  "helcim_in_person",
      +  "quickbooks_payments_invoice_ach",
      +  "freshbooks_invoice_ach",
      +  "wave_invoice_ach",
      +  "xero_invoice_ach",
      +  "xero_bank_transfer",
      +  "gocardless_ach_debit",
      +  "zoho_payments_ach_debit",
      +  "bill_com_invoice_ach",
      +  "honeybook_invoice_ach",
      +  "bonsai_invoice_ach",
      +  "jobber_invoice_ach",
      +  "housecall_pro_invoice_ach",
      +  "melio_ach",
      +  "stripe_ach",
      +  "helcim_ach",
      +  "square_ach",
      +  "paypal_ach",
      +  "zelle_business",
      +  "wise_business_bank",
      +  "payoneer_bank",
      +  "venmo_business",
      +  "cash_app_business",
      +  "paypal_gs",
      +  "square_card_online_square_plus",
      +  "squarespace_payments_card_online_core",
      +  "squarespace_payments_card_in_person_core"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / totals / items / properties / route / enum
      Previous value: -[
      -  "stripe_card",
      -  "square_card",
      -  "paypal_checkout",
      -  "paypal_card",
      -  "helcim_card",
      -  "melio_card",
      -  "shopify_card",
      -  "stripe_terminal",
      -  "square_in_person",
      -  "helcim_in_person",
      -  "melio_ach",
      -  "stripe_ach",
      -  "helcim_ach",
      -  "square_ach",
      -  "paypal_ach",
      -  "zelle_business",
      -  "wise_business_bank",
      -  "payoneer_bank",
      -  "venmo_business",
      -  "cash_app_business",
      -  "paypal_gs"
      -]New value: +[
      +  "quickbooks_payments_invoice_card",
      +  "quickbooks_payments_desktop_invoice_card",
      +  "freshbooks_invoice_card",
      +  "wave_invoice_card",
      +  "xero_invoice_card",
      +  "zoho_payments_card_online",
      +  "bill_com_invoice_card",
      +  "honeybook_invoice_card",
      +  "bonsai_invoice_card",
      +  "housecall_pro_invoice_card",
      +  "godaddy_payments_card_online",
      +  "godaddy_payments_invoice_card",
      +  "wix_payments_card_online",
      +  "squarespace_payments_card_online",
      +  "squarespace_payments_card_online_plus",
      +  "squarespace_payments_card_online_advanced",
      +  "square_card_online",
      +  "square_card_online_square_premium",
      +  "sumup_invoice_card",
      +  "paypal_invoice_card",
      +  "airwallex_card_online",
      +  "squarespace_payments_card_online_core",
      +  "square_card_online_square_plus",
      +  "stripe_card",
      +  "square_card",
      +  "paypal_checkout",
      +  "paypal_card",
      +  "helcim_card",
      +  "melio_card",
      +  "shopify_card",
      +  "quickbooks_payments_card_in_person",
      +  "xero_card_in_person",
      +  "jobber_card_in_person",
      +  "housecall_pro_card_in_person",
      +  "clover_card_in_person_retail_growth",
      +  "godaddy_payments_card_in_person",
      +  "wix_payments_card_in_person",
      +  "wix_payments_tap_to_pay",
      +  "squarespace_payments_card_in_person",
      +  "shopify_payments_card_in_person",
      +  "shopify_payments_card_in_person_grow",
      +  "shopify_payments_card_in_person_advanced",
      +  "shopify_payments_card_in_person_plus",
      +  "square_card_in_person_square_plus",
      +  "square_card_in_person_square_premium",
      +  "lightspeed_card_in_person",
      +  "sumup_card_in_person",
      +  "paypal_pos_card_in_person",
      +  "stripe_tap_to_pay",
      +  "squarespace_payments_card_in_person_core",
      +  "stripe_terminal",
      +  "square_in_person",
      +  "helcim_in_person",
      +  "quickbooks_payments_invoice_ach",
      +  "freshbooks_invoice_ach",
      +  "wave_invoice_ach",
      +  "xero_invoice_ach",
      +  "xero_bank_transfer",
      +  "gocardless_ach_debit",
      +  "zoho_payments_ach_debit",
      +  "bill_com_invoice_ach",
      +  "honeybook_invoice_ach",
      +  "bonsai_invoice_ach",
      +  "jobber_invoice_ach",
      +  "housecall_pro_invoice_ach",
      +  "melio_ach",
      +  "stripe_ach",
      +  "helcim_ach",
      +  "square_ach",
      +  "paypal_ach",
      +  "zelle_business",
      +  "wise_business_bank",
      +  "payoneer_bank",
      +  "venmo_business",
      +  "cash_app_business",
      +  "paypal_gs"
      +]
  3. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral facts: PaidRouter persists only the submitted totals, PII must never be sent, and fee sign is normalized ('either sign works'). It does not state that this is a computation with no side effects on the user's accounts, nor anything about latency or limits (e.g. the 50-row cap), so disclosure is good but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every paragraph is functionally load-bearing for data preparation, but the first sentence is an overstuffed run-on and the whole block is dense prose with no line breaks or bullets despite being a multi-step procedure. Front-loading is weak: the actual submission contract ({route, period_start, ...}) appears inside the first paragraph rather than leading.

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, and the description still conveys what comes back (the effective rate next to the published fee and the cheapest payer route, with the yearly saving in dollars). Combined with the detailed export recipes and privacy constraints, an agent has everything needed to assemble valid input and understand 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?

At 50% schema description coverage the description has to compensate, and it largely does: it restates the row shape exactly, gives concrete route-mapping rules (card rows → stripe_card, terminal → stripe_terminal, us_bank_account → stripe_ach, PayPal checkout vs gs), and clarifies how to derive periods and fee sums. The one gap is payer_pays_by, which the description never explains beyond 'the cheapest route their payers can use' — the enum values and 'any' semantics live only in the schema.

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 opening sentence names the resource concretely: the owner's effective rate from their own exports vs. published fees vs. the cheapest payer route, plus the yearly dollar saving. It is wrapped in a long run-on clause rather than a crisp verb+object ('Calculate X from Y'), and it never names any of the siblings it overlaps with (cheapest_way_to_get_paid, explain_fees, get_fees). An agent can infer the job, but only after parsing a marketing-flavored sentence.

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?

Strong, explicit data-preparation guidance with real exclusions: which Stripe report to export, which PayPal report, keep only reporting_category = charge, and a direct prohibition ('The plain Payouts list export has no per-payment fees; don't use it'). What is missing is when to choose this tool over the siblings that also discuss cheapest routes and fees; that comparison is left implicit.

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