Skip to main content
Glama
0x8687

Meme MCP Server

by 0x8687

forward-email

Forward emails to other recipients by specifying the email ID and destination address, with optional additional messages included.

Instructions

Forward an email to other recipients

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailIdYesThe ID of the email to forward
toYesThe email address to forward to
messageNoAdditional message to include with the forward

Implementation Reference

  • The main handler function that implements the forward-email tool logic by executing the GMAIL_FORWARD_EMAIL action via the Composio toolset and handling the response.
    }, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_FORWARD_EMAIL",
                entityId: userAddress,
                params: args
            });
            
            if (result.successful) {
                return {
                    content: [{ 
                        type: "text", 
                        text: `✅ Email forwarded successfully!\n\nForwarded to: ${args.to}` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to forward email: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error forwarding email:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error forwarding email: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
  • Zod schema defining the input parameters for the forward-email tool: emailId (required), to (required), message (optional).
    emailId: z.string().describe("The ID of the email to forward"),
    to: z.string().describe("The email address to forward to"),
    message: z.string().optional().describe("Additional message to include with the forward"),
  • src/tools.ts:242-280 (registration)
    Full registration of the forward-email tool using server.tool, including name, description, schema, and inline handler.
    server.tool("forward-email", "Forward an email to other recipients", {
        emailId: z.string().describe("The ID of the email to forward"),
        to: z.string().describe("The email address to forward to"),
        message: z.string().optional().describe("Additional message to include with the forward"),
    }, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_FORWARD_EMAIL",
                entityId: userAddress,
                params: args
            });
            
            if (result.successful) {
                return {
                    content: [{ 
                        type: "text", 
                        text: `✅ Email forwarded successfully!\n\nForwarded to: ${args.to}` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to forward email: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error forwarding email:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error forwarding email: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action ('forward') which implies a mutation, but doesn't address permissions, side effects (e.g., whether the original email is modified), rate limits, or error conditions. This leaves significant gaps for a mutation tool.

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 sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., what happens after forwarding), error handling, or return values, leaving the agent with insufficient context for reliable use.

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 description coverage is 100%, so the input schema fully documents all three parameters. The description adds no additional meaning beyond implying 'emailId' and 'to' are required (matching schema) and that 'message' is optional additional content. This meets the baseline for high schema coverage.

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 clearly states the action ('forward') and resource ('an email'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'reply-to-email' or 'send-email' beyond the basic verb, which prevents 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?

The description provides no guidance on when to use this tool versus alternatives like 'reply-to-email' or 'send-email', nor does it mention prerequisites such as needing an existing email ID. It simply states what the tool does without context for selection.

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/0x8687/mcp-gmail-v1'

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