Loyal Spark Loyalty Protocol
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_platform_infoA | Get info about Loyal Spark protocol on Base L2 |
| get_my_profileA | Get authenticated agent's profile |
| list_loyalty_programsA | List loyalty programs owned by the agent's merchant |
| create_loyalty_programA | Get factory calldata to deploy a new ERC-20 loyalty token on Base |
| register_loyalty_programC | Register a deployed token as a loyalty program in the database |
| activate_loyalty_programA | Get activation calldata (unpauseUtility + enableMinting) for an inactive program |
| update_program_statusA | Update program status in database after on-chain activation/pause |
| list_rewardsC | List rewards for a loyalty program by token_address |
| create_rewardB | Create a new reward redeemable with loyalty tokens |
| mint_loyalty_tokensB | Record mint intent and get smart contract call params |
| transfer_loyalty_tokensA | Get calldata to transfer loyalty tokens between wallets |
| get_token_balanceB | Get loyalty token balance and tier info for a customer |
| get_program_analyticsB | Get analytics for your loyalty programs |
| list_marketplace_offersA | List active token trading offers on the marketplace |
| redeem_rewardA | Redeem a reward by providing a verified token transfer transaction hash. Creates a voucher for the customer. |
| use_voucherA | Mark a voucher as used (redeemed by customer at merchant). Merchant-only operation. |
| check_voucher_statusA | Check voucher status by code or ID. Public endpoint — no API key or authentication required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Tools are mostly distinct, though create_loyalty_program vs register_loyalty_program and activate_loyalty_program vs update_program_status operate on similar resources and could cause brief hesitation. Descriptions clarify the deployment vs. registration and calldata generation vs. database update distinctions sufficiently.
Excellent consistency throughout with strict verb_noun snake_case pattern (e.g., create_reward, transfer_loyalty_tokens, check_voucher_status). All 17 tools follow the same convention without deviation.
17 tools is slightly large but justified for the scope, covering full lifecycle: program deployment/registration, token minting/transfers, reward management, voucher handling, marketplace queries, and analytics. Each tool earns its place without redundancy.
Strong coverage of loyalty protocol workflows including deployment, activation, token operations, reward redemption, and voucher lifecycle. Minor gaps exist for reward updates/deletion and explicit pause calldata generation, but agents can work around these using existing tools.