Skip to main content
Glama

generateWallet

Create a new Ethereum wallet with a private key, optionally saving it to environment variables for secure access in blockchain operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveToEnvNoOptional. If true, the private key will be saved to the server's environment variables for future use. Default is false.

Implementation Reference

  • Full registration of the generateWallet MCP tool, including Zod input schema, async handler function that creates a random Ethereum wallet using ethers.Wallet.createRandom(), optionally saves private key to env, and returns address and private key.
      server.tool(
        "generateWallet",
        {
          saveToEnv: z.boolean().optional().describe(
            "Optional. If true, the private key will be saved to the server's environment variables for future use. Default is false."
          )
        },
        async ({ saveToEnv = false }) => {
          try {
            const wallet = ethers.Wallet.createRandom();
            
            if (saveToEnv) {
              process.env.WALLET_PRIVATE_KEY = wallet.privateKey;
              
              // Update the ethersService with the new wallet
              const signer = new ethers.Wallet(wallet.privateKey, ethersService.provider);
              ethersService.setSigner(signer);
            }
            
            return {
              content: [{ 
                type: "text", 
                text: `
    New wallet generated:
    Address: ${wallet.address}
    Private Key: ${wallet.privateKey}
    ${saveToEnv ? "Private key has been saved to environment variables for this session." : ""}
    `
              }]
            };
          } catch (error) {
            return {
              isError: true,
              content: [{ 
                type: "text", 
                text: `Error generating wallet: ${error instanceof Error ? error.message : String(error)}`
              }]
            };
          }
        }
      );
  • Zod schema for generateWallet tool input: optional boolean saveToEnv.
    saveToEnv: z.boolean().optional().describe(
      "Optional. If true, the private key will be saved to the server's environment variables for future use. Default is false."
    )
  • Handler function for generateWallet tool: generates random wallet, optionally persists to env and updates service, returns formatted response.
        async ({ saveToEnv = false }) => {
          try {
            const wallet = ethers.Wallet.createRandom();
            
            if (saveToEnv) {
              process.env.WALLET_PRIVATE_KEY = wallet.privateKey;
              
              // Update the ethersService with the new wallet
              const signer = new ethers.Wallet(wallet.privateKey, ethersService.provider);
              ethersService.setSigner(signer);
            }
            
            return {
              content: [{ 
                type: "text", 
                text: `
    New wallet generated:
    Address: ${wallet.address}
    Private Key: ${wallet.privateKey}
    ${saveToEnv ? "Private key has been saved to environment variables for this session." : ""}
    `
              }]
            };
          } catch (error) {
            return {
              isError: true,
              content: [{ 
                type: "text", 
                text: `Error generating wallet: ${error instanceof Error ? error.message : String(error)}`
              }]
            };
          }
        }
  • Registration of core tools group (including generateWallet) via registerCoreTools call in top-level tools index.
    registerCoreTools(server, ethersService);
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/crazyrabbitLTC/mcp-ethers-server'

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