Skip to main content
Glama

loadWallet

Load an Ethereum wallet by providing a private key to enable blockchain interactions and smart contract operations within the MCP Ethers Wallet server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privateKeyYesThe private key of the wallet to load. Should start with '0x'.
saveToEnvNoOptional. If true, the private key will be saved to the server's environment variables for this session. Default is true.

Implementation Reference

  • The core handler logic for the 'loadWallet' tool. Creates an ethers.js Wallet instance from the provided private key, optionally persists it to process.env.WALLET_PRIVATE_KEY and configures it as the signer on the shared ethersService instance, then returns a success response with the wallet address.
        async ({ privateKey, saveToEnv = true }) => {
          try {
            const wallet = new ethers.Wallet(privateKey);
            
            if (saveToEnv) {
              process.env.WALLET_PRIVATE_KEY = privateKey;
              
              // Update the ethersService with the new wallet
              const signer = new ethers.Wallet(privateKey, ethersService.provider);
              ethersService.setSigner(signer);
            }
            
            return {
              content: [{ 
                type: "text", 
                text: `
    Wallet loaded successfully:
    Address: ${wallet.address}
    ${saveToEnv ? "Private key has been saved to environment variables for this session." : ""}
    `
              }]
            };
          } catch (error) {
            return createErrorResponse(error, 'loading wallet');
          }
        }
  • Zod input schema validation for the 'loadWallet' tool parameters: requires a privateKey string and optional saveToEnv boolean (defaults to true).
    {
      privateKey: z.string().describe(
        "The private key of the wallet to load. Should start with '0x'."
      ),
      saveToEnv: z.boolean().optional().describe(
        "Optional. If true, the private key will be saved to the server's environment variables for this session. Default is true."
      )
    },
  • Registration of the 'loadWallet' MCP tool on the server using server.tool(), including inline schema and handler implementation within the registerCoreTools function.
      server.tool(
        "loadWallet",
        {
          privateKey: z.string().describe(
            "The private key of the wallet to load. Should start with '0x'."
          ),
          saveToEnv: z.boolean().optional().describe(
            "Optional. If true, the private key will be saved to the server's environment variables for this session. Default is true."
          )
        },
        async ({ privateKey, saveToEnv = true }) => {
          try {
            const wallet = new ethers.Wallet(privateKey);
            
            if (saveToEnv) {
              process.env.WALLET_PRIVATE_KEY = privateKey;
              
              // Update the ethersService with the new wallet
              const signer = new ethers.Wallet(privateKey, ethersService.provider);
              ethersService.setSigner(signer);
            }
            
            return {
              content: [{ 
                type: "text", 
                text: `
    Wallet loaded successfully:
    Address: ${wallet.address}
    ${saveToEnv ? "Private key has been saved to environment variables for this session." : ""}
    `
              }]
            };
          } catch (error) {
            return createErrorResponse(error, 'loading wallet');
          }
        }
      );
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