Skip to main content
Glama
0x8687

Meme MCP Server

by 0x8687

create-draft

Generate email drafts by specifying recipient, subject, and body content to compose messages for communication purposes.

Instructions

Create an email draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesThe email address of the recipient
subjectYesThe subject of the email
bodyYesThe body of the email

Implementation Reference

  • The async handler function that creates an email draft by executing the Composio 'GMAIL_DRAFT_EMAIL' action and returns success or error messages.
    }, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_DRAFT_EMAIL",
                entityId: userAddress,
                params: args
            });
            
            if (result.successful) {
                return {
                    content: [{ 
                        type: "text", 
                        text: `📝 Draft created successfully!\n\nDraft ID: ${(result.data?.response_data as any)?.id}\nTo: ${args.to}\nSubject: ${args.subject}` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to create draft: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error creating draft:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error creating draft: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
  • Zod input schema defining parameters for the create-draft tool: recipient email, subject, and body.
    to: z.string().describe("The email address of the recipient"),
    subject: z.string().describe("The subject of the email"),
    body: z.string().describe("The body of the email"),
  • src/tools.ts:283-283 (registration)
    The server.tool call that registers the 'create-draft' tool with its description, schema, and handler.
    server.tool("create-draft", "Create an email draft", {
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. 'Create an email draft' implies a write operation but doesn't specify whether it requires authentication, what happens on failure, if drafts are saved immediately, or any rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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 zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately.

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 insufficient. It doesn't explain what happens after creation (e.g., where the draft is stored, if it returns a draft ID), authentication requirements, or error conditions. Given the complexity of email operations, more context is needed.

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%, with all three parameters ('to', 'subject', 'body') clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it 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 'Create an email draft' clearly states the verb ('Create') and resource ('an email draft'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'send-email' or 'send-draft', which would require more specificity about what distinguishes draft creation from sending.

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 'send-email' or 'send-draft'. There's no mention of prerequisites (e.g., needing a connected Gmail account) or typical use cases (e.g., saving an email for later editing).

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