Skip to main content
Glama
jhw7500

Email MCP Server

by jhw7500

send_email

Send emails directly from applications using SMTP protocol. Specify recipient, subject, and body to dispatch messages through the Email MCP Server.

Instructions

이메일을 발송합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes수신자 이메일 주소
subjectYes제목
bodyYes본문 (텍스트)

Implementation Reference

  • The handler logic for the 'send_email' tool, which validates the tool name and uses nodemailer to send the email.
      if (toolName !== "send_email") {
        return { content: [{ type: "text" as const, text: `Unknown tool: ${toolName}` }], isError: true };
      }
      try {
        const { to, subject, body } = args as { to: string; subject: string; body: string };
        const transporter = nodemailer.createTransport({
          host: smtpConfig.host,
          port: smtpConfig.port,
          secure: true,
          auth: { user: smtpConfig.user, pass: smtpConfig.password },
        });
        await transporter.sendMail({ from: smtpConfig.user, to, subject, text: body });
        return {
          content: [{ type: "text" as const, text: `이메일 발송 완료: "${subject}" → ${to}` }],
        };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        return { content: [{ type: "text" as const, text: `발송 오류: ${msg}` }], isError: true };
      }
    };
  • The schema definition for the 'send_email' tool, specifying input arguments.
    {
      name: "send_email",
      description: "이메일을 발송합니다.",
      inputSchema: {
        type: "object" as const,
        properties: {
          to: { type: "string", description: "수신자 이메일 주소" },
          subject: { type: "string", description: "제목" },
          body: { type: "string", description: "본문 (텍스트)" },
        },
        required: ["to", "subject", "body"],
      },
    },
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action but doesn't describe any behavioral traits such as permissions needed, whether it's idempotent, error handling, or side effects. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 appropriately sized for a simple tool, though it could be more informative. The structure is front-loaded but minimal.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like success/failure responses, authentication needs, or usage context. For a tool that sends emails, more detail is warranted.

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 schema already documents all parameters (to, subject, body). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 '이메일을 발송합니다' (sends an email) states the basic action but lacks specificity about scope or resource. It doesn't distinguish from siblings like fetch_email_thread or search_emails, which are read operations versus this write operation. The purpose is clear but minimal.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites like authentication, rate limits, or when to choose send_email over other email-related tools. The description offers no context for usage decisions.

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/jhw7500/email-mcp-server'

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