Skip to main content
Glama

azeth_create_account

Give an AI agent or service an on-chain smart account with guardian spending limits and ERC-8004 trust registry registration, all in one atomic transaction.

Instructions

Deploy a new Azeth smart account with guardian guardrails and register it on the ERC-8004 trust registry.

Use this when: An AI agent or service needs its own on-chain identity with spending limits and trust registry presence. One EOA can own multiple smart accounts.

Single atomic transaction: deploys smart account proxy, installs all 4 modules (Guardian, TrustRegistry, PaymentAgreement, Reputation), registers on ERC-8004, and permanently revokes factory access.

Returns: The deployed smart account address, trust registry token ID, and transaction hash.

Gas: when the Azeth server relay is reachable, creation is sponsored (EIP-712 gasless relay — no ETH required, and testnet USDC is auto-dripped). When the relay is unreachable, creation FALLS BACK to a direct transaction paid by your EOA (requires ETH for gas). The response's "creationPath" field reports which path was used ("gasless-relay" or "direct").

Guardian: By default, the guardian is derived from AZETH_GUARDIAN_KEY env var. If not set, falls back to self-guardian (owner address). For production, always use a separate guardian key. Set AZETH_GUARDIAN_KEY in your .env file.

Example: { "name": "PriceFeedBot", "entityType": "service", "description": "Real-time crypto price data", "capabilities": ["price-feed", "market-data"] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for this participant in the trust registry.
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").
endpointNoOptional HTTP endpoint (http:// or https://) where this participant can be reached.
guardianNoGuardian address for co-signing operations that exceed spending limits. If omitted, derived from AZETH_GUARDIAN_KEY env var. If neither is set, defaults to the owner address (self-guardian, NOT recommended for production).
entityTypeYesParticipant type: "agent" (AI agent), "service" (API/oracle), or "infrastructure" (bridge/relay).
descriptionYesHuman-readable description of what this participant does.
capabilitiesYesList of capabilities this participant offers (e.g., ["swap", "price-feed", "translation"]).
maxTxAmountUSDNoMax USD per transaction (default: $100 testnet, $50 mainnet).
dailySpendLimitUSDNoMax USD per day (default: $1000 testnet, $500 mainnet).
emergencyWithdrawToNoAddress where funds are sent during emergency withdrawal. Defaults to the owner EOA address (derived from AZETH_PRIVATE_KEY). Must be a trusted address you control — this is your recovery destination.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that the action is a single atomic transaction, installs 4 modules, permanently revokes factory access, details gas sponsorship and fallback, explains guardian derivation from environment variables, and specifies return fields (address, token ID, tx hash, creationPath). This is comprehensive and goes beyond basic expectations.

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?

The description is well-structured with clear sections: purpose, usage scenario, atomic details, returns, gas info, guardian setup, and an example. It is somewhat lengthy but every sentence adds necessary information without redundancy. Front-loaded with the primary purpose.

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

Completeness4/5

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

Given 10 parameters, no output schema, and no annotations, the description covers creation behavior, gas handling, guardian configuration, defaults, and includes an example. It does not exhaustively cover all edge cases or errors, but it provides sufficient context for an AI agent to understand invocation and results.

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% with all parameters described. The description adds significant value by explaining defaults (chain from env var, guardian from env var, explicit default spending limits per network), providing an example, and clarifying behavior for optional parameters like 'emergencyWithdrawTo'. This enriches the schema information.

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?

The description clearly states the action ('Deploy a new Azeth smart account') and the resource ('register it on the ERC-8004 trust registry'). It distinguishes from sibling tools like 'azeth_accounts' (list accounts) or 'azeth_balance' (check balance) by focusing on creation and registration.

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

Usage Guidelines4/5

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

The description explicitly says when to use: 'An AI agent or service needs its own on-chain identity with spending limits and trust registry presence.' It also mentions that one EOA can own multiple accounts, providing context. It does not explicitly state when not to use, but the purpose is clear enough to avoid misuse.

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