Skip to main content
Glama

sign-message

Sign messages securely using MetaMask to verify identity and authenticate blockchain transactions without exposing private keys.

Instructions

Sign a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to sign.

Implementation Reference

  • The execute function implements the core logic of the 'sign-message' tool: extracts the message from args, calls wagmi's signMessage, returns the hash in a structured content response, with error handling.
    execute: async (args, { log }) => {
      try {
        const message = args.message;
        const result = await signMessage(wagmiConfig, {
          message,
        });
        return {
          content: [
            {
              type: "text",
              text: JSONStringify({
                hash: result,
              }),
            },
          ],
        };
      }
      catch (error) {
        log.debug((error as Error).message);
        throw error;
      }
    },
  • Zod schema defining the input parameters for the tool: a single 'message' string.
    parameters: z.object({
      message: z.string().describe("Message to sign."),
    }),
  • The registration function that adds the 'sign-message' tool to the FastMCP server using server.addTool, including name, description, schema, and handler.
    export function registerSignMessageTools(server: FastMCP, wagmiConfig: Config): void {
      server.addTool({
        name: "sign-message",
        description: "Sign a message.",
        parameters: z.object({
          message: z.string().describe("Message to sign."),
        }),
        execute: async (args, { log }) => {
          try {
            const message = args.message;
            const result = await signMessage(wagmiConfig, {
              message,
            });
            return {
              content: [
                {
                  type: "text",
                  text: JSONStringify({
                    hash: result,
                  }),
                },
              ],
            };
          }
          catch (error) {
            log.debug((error as Error).message);
            throw error;
          }
        },
      });
    };
  • Top-level call to registerSignMessageTools within the central registerTools function, invoked as part of initializing all tools.
    registerSignMessageTools(server, wagmiConfig);
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Sign a message' implies a write/mutation operation, but it doesn't disclose any behavioral traits such as required permissions, whether it's reversible, rate limits, or what the output looks like (e.g., a signature string). This is inadequate for a tool with potential security or state-changing implications.

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 extremely concise ('Sign a message.') with no wasted words, making it front-loaded and easy to parse. Every word earns its place by directly stating the tool's action, though this conciseness comes at the cost of detail.

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 a signing operation (likely involving cryptography or blockchain), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'signing' entails in this context, what the result is, or any dependencies, leaving significant gaps for an agent to understand and use the tool effectively.

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?

The input schema has 100% description coverage, with the 'message' parameter fully documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., format constraints or examples), so it meets the baseline of 3 for high schema coverage without compensating value.

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

Purpose3/5

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

The description 'Sign a message' clearly states the verb ('sign') and resource ('a message'), providing a basic understanding of the tool's function. However, it lacks specificity about what type of signing (e.g., cryptographic, blockchain) or context, and doesn't distinguish it from sibling tools like 'verify-message' beyond the obvious verb difference.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an account or connection), exclusions, or comparisons to siblings like 'verify-message' or 'send-transaction', leaving the agent to infer usage from the name alone.

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/Xiawpohr/metamask-mcp'

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