For legacy ERC-20 programs: returns unpauseUtility + enableMinting calldata. For B20 programs: no-op (already active).
| Name | Required | Description | Default |
|---|---|---|---|
| token_address | Yes | Token contract address (0x...) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool returns calldata rather than performing the activation itself, and that it is a no-op for B20. This is important behavioral context. It doesn't cover side effects or output format, but the main behavior is transparent.
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 one concise sentence that conveys both conditional behaviors without redundancy. Every word contributes value.
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?
The tool is simple (one parameter, no output schema) and the description covers both program-type branches. It could be more complete by explaining the format of the returned calldata or defining B20, but the essential behavior is sufficiently described for a low-complexity tool.
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?
The single parameter token_address has 100% schema coverage, so the schema fully documents it. The description adds meaning by implying the token address identifies whether the program is legacy ERC-20 or B20, but does not add new syntax or format details beyond the schema.
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 what the tool does: it returns unpauseUtility + enableMinting calldata for legacy ERC-20 programs and is a no-op for B20 programs. This distinguishes the behavior across program types and is more specific than simply restating the tool name.
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?
The description provides explicit usage conditions: use for legacy ERC-20 programs, and explicitly states that for B20 programs it is a no-op (already active), which serves as a clear when-not-to-use. This effectively guides the agent on when to select this tool.
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.