Hosted MCP server for commerce math: fees, invoice totals, discounts, proration, installment plans.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Score is being calculated. Check back soon.
charge_to_netCharge To NetCompute the gross price to charge so you net a target after fees. FREE.
'Charge X to receive Y' after percentage + fixed processor fees. Typical input {"net_target": 100, "pct_fee": 2.9, "fixed_fee": 0.30} returns {"charge": 103.4, "fee": 3.4, "net": 100.0}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "net_target > 0 and pct_fee < 100 required"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| pct_fee | No | Processor percentage fee, below 100, e.g. 2.9 for 2.9%. Default 2.9. | |
| fixed_fee | No | Processor fixed fee per charge. Default 0.30. | |
| net_target | Yes | The amount you want to receive after fees; must be greater than 0. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
discount_stackDiscount StackStack discounts correctly: sequential vs additive comparison. PREMIUM (license).
The two methods differ — this shows both, the final price, and the true total discount. Typical input {"price": 200, "discounts_pct": [20, 10]} returns {"original": 200, "sequential_price": 144.0, "sequential_total_discount_pct": 28.0, "additive_price": 140.0, "difference": 4.0, "note": "..."}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "price > 0 and at least one discount required"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| price | Yes | Original price before discounts; must be greater than 0. | |
| discounts_pct | Yes | Discount percentages in the order applied, at least one, e.g. [20, 10] for 20% then 10%. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
installment_planInstallment PlanSplit a total into an installment schedule with optional deposit. PREMIUM (license).
Rounding remainders land on the final payment so the schedule always sums exactly. Typical input {"total": 1000, "installments": 3, "deposit_pct": 10} returns {"deposit": 100.0, "payments": [300.0, 300.0, 300.0], "check_sum": 1000.0}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "total > 0 and 1-36 installments"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | Full amount to split; must be greater than 0. | |
| deposit_pct | No | Optional upfront deposit as a percentage of total, e.g. 10 for 10%. Default 0. | |
| installments | Yes | Number of payments after the deposit; 1 to 36. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
invoice_totalInvoice TotalTotal an invoice: per-line totals, subtotal, discount, tax, grand total. FREE.
Typical input {"line_items": [{"desc": "Design", "qty": 2, "unit_price": 50}], "tax_pct": 8.5, "discount_pct": 10} returns {"lines": [{"desc": "Design", "qty": 2, "unit_price": 50, "line_total": 100.0}], "subtotal": 100.0, "discount": 10.0, "tax": 7.65, "total": 97.65}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "line_items must contain at least one item,"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| tax_pct | No | Tax percentage applied after the discount, e.g. 8.5. Default 0. | |
| line_items | Yes | At least one line item object {"desc": str, "qty": number, "unit_price": number}; the first 100 items are used. | |
| discount_pct | No | Discount percentage applied to the subtotal. Default 0. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
processor_feesProcessor FeesBreak down payment-processor fees: fee, net, and effective rate. FREE.
Uses editable presets for stripe/paypal/square/shopify (verify current rates) or your own custom_pct + custom_fixed. Typical input {"amount": 1000, "processor": "stripe", "transactions": 10} returns {"gross": 1000, "fee": 32.0, "net": 968.0, "effective_rate_pct": 3.2, "note": "..."}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "amount must be > 0, transactions >= 1"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | Total gross amount processed; must be greater than 0. | |
| processor | No | One of "stripe", "paypal", "square", "shopify", or "custom". Default "stripe". | stripe |
| custom_pct | No | Percentage fee used when processor is "custom", e.g. 2.5 for 2.5%. | |
| custom_fixed | No | Fixed per-transaction fee used when processor is "custom", e.g. 0.25. | |
| transactions | No | How many transactions the amount is spread across; at least 1. Default 1. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
prorationProrationCompute a prorated charge or refund for a partial billing period. PREMIUM (license).
Typical input {"amount_per_period": 90, "days_used": 10, "days_in_period": 30} returns {"days_used": 10, "days_in_period": 30, "prorated_charge": 30.0, "prorated_refund": 60.0, "answer": 30.0}. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "need amount > 0 and 0 <= days_used <= days_in_period"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Required | Description | Default |
|---|---|---|---|
| days_used | Yes | Days of the period consumed; 0 to days_in_period. | |
| refund_mode | No | If true, "answer" is the refund amount instead of the charge. Default false. | |
| days_in_period | No | Length of the billing period in days; at least 1. Default 30. | |
| amount_per_period | Yes | Full-period price; must be greater than 0. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!