Skip to main content
Glama
lordbasilaiassistant-sudo

base-multi-wallet-mcp

create_wallet

Generate a new random wallet for coordinated trading on Base, storing the private key in-memory only for the current session.

Instructions

Generate a new random wallet. Returns address (private key stored in-memory for session only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional name/label for the wallet

Implementation Reference

  • Handler function for the create_wallet tool. It generates a new ethers wallet, adds it to the in-memory 'wallets' list, and returns the wallet details.
    async function handleCreateWallet(
      args: z.infer<typeof CreateWalletSchema>
    ): Promise<string> {
      const randomWallet = ethers.Wallet.createRandom();
      const label = args.label || `wallet-${wallets.length + 1}`;
    
      wallets.push({
        address: randomWallet.address,
        privateKey: randomWallet.privateKey,
        label,
      });
    
      return JSON.stringify(
        {
          success: true,
          address: randomWallet.address,
          label,
          message: `Wallet created. Private key is stored in-memory for this session only.`,
          total_managed: wallets.length,
        },
        null,
        2
      );
    }
  • Input schema for the create_wallet tool using Zod.
    const CreateWalletSchema = z.object({
      label: z.string().optional().describe("Optional name/label for the wallet"),
    });
  • src/index.ts:761-774 (registration)
    Registration of the create_wallet tool in the MCP server.
    {
      name: "create_wallet",
      description:
        "Generate a new random wallet. Returns address (private key stored in-memory for session only).",
      inputSchema: {
        type: "object" as const,
        properties: {
          label: {
            type: "string",
            description: "Optional name/label for the wallet",
          },
        },
      },
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden and successfully discloses critical security behavior: private keys are stored 'in-memory for session only'. It also clarifies the return value (address).

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?

Two efficient sentences with zero waste. The first states the action, the second provides essential security context about key persistence. Front-loaded and appropriately sized.

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?

No output schema exists, and the description compensates by stating the return value (address) and critical security constraints. Adequate for a single-parameter tool with these security implications.

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

Parameters3/5

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

Schema coverage is 100% (label is fully described in schema). The description adds no additional parameter context, meeting the baseline for high-coverage schemas.

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 uses a specific verb ('Generate') with clear resource ('wallet') and distinguishes from sibling 'import_wallet' by specifying 'new random wallet'.

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 explicit guidance on when to use create_wallet versus the sibling 'import_wallet'. The agent must infer that 'random' implies creating new keys while 'import' is for existing ones.

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/lordbasilaiassistant-sudo/base-multi-wallet-mcp'

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