Skip to main content
Glama
jhw7500

Email MCP Server

by jhw7500

read_email

Retrieve complete email content including body text and attachment lists by specifying the email ID. This tool accesses messages from email servers for viewing and analysis.

Instructions

특정 이메일의 전체 내용을 읽습니다. 본문과 첨부파일 목록을 포함합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes이메일 ID (list_emails에서 반환된 id)

Implementation Reference

  • Implementation of the 'read_email' tool handler. It uses the POP3 client to fetch email details by ID and formats the output.
    case "read_email": {
      const id = args.id as number;
      const email = await withConnection(config, (client) => client.getEmail(id));
    
      let text =
        `**${email.subject}**\n` +
        `From: ${email.from}\n` +
        `To: ${email.to}\n` +
        (email.cc ? `CC: ${email.cc}\n` : "") +
        `Date: ${email.date ? new Date(email.date).toLocaleString("ko-KR") : ""}\n\n` +
        `---\n\n${email.body || "(본문 없음)"}`;
    
      if (email.attachments.length > 0) {
        text +=
          `\n\n---\n**첨부파일 (${email.attachments.length}개):**\n` +
          email.attachments
            .map((a) => `- ${a.filename} (${(a.size / 1024).toFixed(1)}KB)`)
            .join("\n");
      }
      return { content: [{ type: "text" as const, text }] };
    }
  • Tool definition and input schema for 'read_email'.
      name: "read_email",
      description: "특정 이메일의 전체 내용을 읽습니다. 본문과 첨부파일 목록을 포함합니다.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: { type: "number", description: "이메일 ID (list_emails에서 반환된 id)" },
        },
        required: ["id"],
      },
    },
Behavior2/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. It states the tool reads content, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or whether it returns structured data. The description is minimal and lacks context beyond the basic action.

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 very concise and front-loaded, consisting of a single sentence that directly states the tool's function. There is no wasted language, and every word contributes to understanding the purpose efficiently.

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 tool's complexity (reading email content with attachments) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error cases, or how attachments are handled (e.g., as metadata or links). For a tool with no structured output, more context is needed to guide the agent 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?

Schema description coverage is 100%, with the parameter 'id' documented as 'email ID (from list_emails)'. The description doesn't add meaning beyond this, as it doesn't explain parameter usage or constraints. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra details.

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 tool's purpose: 'read the full content of a specific email, including body and attachment list.' It specifies the verb ('read') and resource ('specific email'), and mentions what content is included. However, it doesn't explicitly differentiate from siblings like 'fetch_email_thread' or 'list_emails' beyond implying it's for a single email.

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 email ID from 'list_emails'), exclusions, or comparisons to siblings like 'fetch_recent_emails' or 'search_emails'. Usage is implied only by the action described.

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