Skip to main content
Glama

azeth_whitelist_token

Add or remove a token from your smart account's guardian whitelist to enable payment agreements and executor-module operations.

Instructions

Add or remove a token from your smart account's guardian whitelist.

Use this when: You need to whitelist a new token for payment agreements or other executor-module operations. Newly created accounts already have ETH, USDC, and WETH whitelisted by default.

Why it matters: The GuardianModule enforces a token whitelist for automated operations (payment agreements, swap execution). Owner-signed transfers bypass the whitelist, but executor modules like PaymentAgreementModule require the token to be whitelisted.

Returns: Transaction hash confirming the whitelist update.

Note: Only the account owner can update their own whitelist. If a guardian is configured, whitelisting a token is a guardrail change that requires guardian co-signature — the call returns a GUARDIAN_COSIGN_REQUIRED error with guidance until the guardian signs.

Example: { "token": "0x036CbD53842c5426634e7929541eC2318f3dCF7e", "allowed": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").
tokenYesToken contract address to whitelist/delist. Use "0x0000000000000000000000000000000000000000" for native ETH.
allowedYestrue to whitelist the token, false to remove it from the whitelist.
smartAccountNoSmart account address, name, or "#N". Defaults to first smart account.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses behavioral traits: requires owner-only access, may require guardian co-signature, returns transaction hash, and mentions possible error. Lacks details on potential side effects (e.g., impacts of removing a whitelisted token with active agreements), but overall informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-organized with labeled sections (Use this when, Why it matters, Returns, Note, Example), front-loading the core purpose. Slightly verbose with 'Why it matters' overlapping usage guidelines, but still efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no output schema, description fully explains return value (transaction hash), error conditions (GUARDIAN_COSIGN_REQUIRED), default whitelist, and provides an example. Covers all necessary context for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds value with example, note about zero address for native ETH, and context for 'allowed.' While schema already covers parameters well, the description enhances understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Add or remove a token from your smart account's guardian whitelist,' specifying the verb (add/remove) and resource (token whitelist). Distinguishes from sibling tool azeth_whitelist_protocol by focusing on tokens.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides 'Use this when' section with specific use cases (payment agreements, executor-module operations) and notes default whitelist. Also explains when not to use (owner-signed transfers bypass) and conditions requiring guardian co-signature, giving clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azeth-protocol/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server