Export customer data for a specific loyalty program. Returns wallet addresses, voucher stats, balances, and tier info. Use for analytics, segmentation, and personalized offers.
| Name | Required | Description | Default |
|---|---|---|---|
| token_address | Yes | Token address of the loyalty program |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It mentions the return payload (wallet addresses, stats, balances, tier info) and implies a read operation, but does not disclose authentication needs, rate limits, export size caps, or any side effects. This is moderate transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences: the first states the core action, the second lists return fields and use cases. Every word earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one well-documented parameter and no output schema, the description adequately covers the main purpose, return fields, and typical uses. It could mention export format or limits, but it remains sufficient for an agent to understand the tool's scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with 'Token address of the loyalty program' fully describing the sole parameter. The description's phrase 'for a specific loyalty program' adds no further meaning beyond the schema, so it adds minimal value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb 'Export' and resource 'customer data for a specific loyalty program', and enumerates the returned data types. This distinguishes it from sibling tools like create_loyalty_program or get_program_analytics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides usage context with 'Use for analytics, segmentation, and personalized offers,' giving clear intended scenarios. However, it does not explicitly mention when not to use it or suggest alternative tools, so it stops short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes, such as mint_loyalty_tokens vs earn_points (both mint loyalty tokens with fee bundles), create_loyalty_program vs register_loyalty_program (deploy vs register existing token), and activate_loyalty_program vs update_program_status (both manage program status). Some pairs like check_voucher_status and list_gift_certificates also overlap on voucher/certificate tracking. However, descriptions are detailed enough to reduce ambiguity for careful agents.
Most tools follow a consistent verb_noun snake_case pattern (e.g., create_reward, list_loyalty_programs). Subtle deviations include earn_points vs mint_loyalty_tokens (different verbs for similar mint operations) and use_voucher vs redeem_reward (different verb styles for redemption). Overall, the naming is predictable and understandable.
With 39 tools, this server is bloated for a loyalty platform. The addition of Bazaar discovery/payment tools and report management expands the scope, but many tools overlap or cover minor variations (e.g., two workflow planners: generate_program_defaults and get_program_workflow_status). A leaner set of 20-25 tools would be more appropriate.
The tool surface covers the full loyalty program lifecycle: creation, activation, registration, token minting/transfer, rewards, gift certificates, vouchers, offers, customer export, analytics, and reports. Notable gaps include no CRUD for personalized offers (only create), no edit capability for rewards (only status changes), and no direct function to list all vouchers by merchant (only status check by code). These are minor workarounds.