Skip to main content
Glama

ethSign

Sign Ethereum data for authentication or verification using hex-formatted input with optional network provider selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe data to sign. Will be converted to hex if not already in hex format.
providerNoOptional. Either a network name or custom RPC URL. Use getAllNetworks to see available networks and their details, or getNetwork to get info about a specific network. You can use any network name returned by these tools as a provider value.

Implementation Reference

  • The handler function implements eth_sign by signing hex-encoded data using the loaded wallet's signMessage method with ethers.getBytes. It checks for wallet availability, converts non-hex data to hex, signs it, and returns the signature and signer address.
    try {
      // First check if a wallet exists
      const wallet = await ethersService.getWallet(provider);
      if (!wallet) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: "No wallet available to sign data. Please create or load a wallet first."
          }]
        };
      }
      
      // Ensure data is in hex format
      let hexData = data;
      if (!data.startsWith("0x")) {
        // Convert string to hex
        hexData = "0x" + Buffer.from(data).toString("hex");
      }
      
      // Sign the data using eth_sign
      // Note: ethers.js v6 doesn't have a direct eth_sign method, so we're using signMessage as an alternative
      // In a real implementation, you'd use a provider's send method with eth_sign
      const signature = await wallet.signMessage(ethers.getBytes(hexData));
      
      return {
        content: [{ 
          type: "text", 
          text: JSON.stringify({
            data: hexData,
            signature,
            signer: wallet.address
          }, null, 2)
        }]
      };
    } catch (error) {
      return {
        isError: true,
        content: [{ 
          type: "text", 
          text: `Error using eth_sign: ${error instanceof Error ? error.message : String(error)}`
        }]
      };
    }
  • Input schema using Zod: 'data' (string to sign, auto-converted to hex) and optional 'provider' (network reference).
      data: z.string().describe(
        "The data to sign. Will be converted to hex if not already in hex format."
      ),
      provider: z.string().optional().describe(PROVIDER_DESCRIPTION)
    },
  • Registration of the 'ethSign' tool on the MCP server using server.tool(), providing name, input schema, and handler function.
    "ethSign",
    {
      data: z.string().describe(
        "The data to sign. Will be converted to hex if not already in hex format."
      ),
      provider: z.string().optional().describe(PROVIDER_DESCRIPTION)
    },
    async ({ data, provider }) => {
      try {
        // First check if a wallet exists
        const wallet = await ethersService.getWallet(provider);
        if (!wallet) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: "No wallet available to sign data. Please create or load a wallet first."
            }]
          };
        }
        
        // Ensure data is in hex format
        let hexData = data;
        if (!data.startsWith("0x")) {
          // Convert string to hex
          hexData = "0x" + Buffer.from(data).toString("hex");
        }
        
        // Sign the data using eth_sign
        // Note: ethers.js v6 doesn't have a direct eth_sign method, so we're using signMessage as an alternative
        // In a real implementation, you'd use a provider's send method with eth_sign
        const signature = await wallet.signMessage(ethers.getBytes(hexData));
        
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              data: hexData,
              signature,
              signer: wallet.address
            }, null, 2)
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error using eth_sign: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
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