KiezelPay Sales MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sales_summaryA | Get the KiezelPay account sales summary: current balance, total purchases, total income, active trials, total paid out, and next/previous payout details. |
| get_sales_todayA | Get today's sales: your number of purchases, revenue (amount), and your rank among KiezelPay merchants for the day. Uses the local timezone for the day boundary. |
| get_sales_yesterdayA | Get yesterday's sales: your number of purchases, revenue (amount), and your rank among KiezelPay merchants for the day. Uses the local timezone for the day boundary. |
| get_purchase_historyA | Get recent individual purchases. Each record includes paidDate, product, productId, country, platform, device, gross totalAmount, net amountToPayOut, status, and isRefunded. Use for detailed, purchase-level questions. |
| list_productsA | List the distinct product names sold recently, derived from purchase history. Use this to discover which products exist before analyzing one. |
| get_product_salesA | Get aggregated sales for a single product derived from purchase history: purchase count, first/last sale, and breakdowns by country, platform, and trigger. Includes revenue if the history records carry a price. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-product | Analyze one product's recent sales performance. |
| trend-product | Describe the sales trend over time for one product. |
| predict-product | Estimate the near-term sales trajectory for one product (heuristic, not a forecast). |
| sales-report | Produce an executive summary of overall account sales. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| products_resource |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of sales data: products, account summary, daily stats, raw purchases, and product-level aggregates. The only close pair, get_sales_today and get_sales_yesterday, are clearly separated by the day in their names and descriptions.
All tools follow a consistent verb_noun pattern (list_products, get_sales_summary, get_sales_today, get_sales_yesterday, get_purchase_history, get_product_sales). The mix of 'list' and 'get' is standard and predictable, with no camelCase or chaotic variations.
Six tools is well-scoped for a sales-focused MCP server. Each tool covers a distinct need without redundancy, making the set feel intentional and manageable.
The tool surface covers the core sales questions: summary, daily performance, raw history, product listing, and per-product breakdowns. Minor gaps exist, such as no arbitrary date-range sales tool or explicit trial/refund analytics, but these can be worked around via purchase history and product sales.