Skip to main content
Glama
kukapay

wallet-generator-mcp

generateWallets

Batch-generates Ethereum wallets and supports EVM-compatible chains for efficient wallet creation in bulk.

Instructions

Batch-generating ethereum wallets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:19-58 (handler)
    Handler function that generates the specified number (1-100) of random Ethereum wallets using ethers.Wallet.createRandom(). Each wallet includes address, privateKey, and mnemonic phrase. Returns a JSON-formatted text response or error.
    async ({ count }) => {
      try {
        const wallets = [];
        // Generate the specified number of random wallets
        for (let i = 0; i < count; i++) {
          const wallet = ethers.Wallet.createRandom();
          wallets.push({
            address: wallet.address,
            privateKey: wallet.privateKey,
            mnemonic: wallet.mnemonic.phrase,
          });
        }
    
        // Return the generated wallets in JSON format
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                wallets,
                null,
                2
              ),
            },
          ],
          isError: false,
        };
      } catch (error) {
        // Return an error message if wallet generation fails
        return {
          content: [
            {
              type: "text",
              text: `Error generating wallets: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema: 'count' parameter (number, min 1, max 100, default 1).
    z.object({
      count: z.number().min(1).max(100).default(1), // Limit the number of wallets to generate (1-100)
    }),
  • index.js:13-59 (registration)
    MCP server tool registration for 'generateWallets': includes name, description, Zod schema, and handler function.
    server.tool(
      "generateWallets",
      "Batch-generating ethereum wallets",
      z.object({
        count: z.number().min(1).max(100).default(1), // Limit the number of wallets to generate (1-100)
      }),
      async ({ count }) => {
        try {
          const wallets = [];
          // Generate the specified number of random wallets
          for (let i = 0; i < count; i++) {
            const wallet = ethers.Wallet.createRandom();
            wallets.push({
              address: wallet.address,
              privateKey: wallet.privateKey,
              mnemonic: wallet.mnemonic.phrase,
            });
          }
    
          // Return the generated wallets in JSON format
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  wallets,
                  null,
                  2
                ),
              },
            ],
            isError: false,
          };
        } catch (error) {
          // Return an error message if wallet generation fails
          return {
            content: [
              {
                type: "text",
                text: `Error generating wallets: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a write operation ('generating') but doesn't disclose behavioral traits like security implications (e.g., private key handling), rate limits, or output format. The description adds minimal value beyond the basic action.

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

Conciseness5/5

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

The description is a single, efficient phrase ('Batch-generating ethereum wallets') with zero wasted words, clearly front-loading the core action. It's appropriately sized for a no-parameter tool.

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

Completeness2/5

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

Given the complexity of generating cryptographic wallets (a sensitive operation), the description is incomplete. No annotations or output schema exist to clarify safety, return values, or error handling, leaving significant gaps for an AI agent.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description doesn't need to add parameter details, so it meets the baseline for this scenario.

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

Purpose4/5

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

The description 'Batch-generating ethereum wallets' clearly states the verb ('generating') and resource ('ethereum wallets'), with 'batch-' indicating multiple outputs. However, it lacks sibling tools for differentiation, preventing a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool, such as for testing, bulk account creation, or specific blockchain contexts. The absence of sibling tools means no alternative comparisons are needed, but basic usage context is missing.

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

Related 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/kukapay/wallet-generator-mcp'

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