Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

get_mail_detail

Retrieve detailed information about a specific email from your Naver Mail account, including content and metadata, by providing the email's unique identifier.

Instructions

특정 메일의 상세 정보 조회

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes조회할 메일의 UID
formatNo출력 형태 (json: JSON 형태, text: 읽기 쉬운 텍스트(내용은 없음))json

Implementation Reference

  • The handler for 'get_mail_detail' tool, which fetches a specific email by UID from the IMAP server and formats the response.
    elif name == "get_mail_detail":
        uid = args.get("uid")
        output_format = args.get("format", "json")
    
        if not uid:
            return [TextContent(type="text", text="UID가 필요합니다.")]
    
        # 특정 UID의 메일 가져오기
        with MailBox("imap.naver.com").login(NAVER_ID, NAVER_PASSWORD, "INBOX") as mailbox:
            mails = list(mailbox.fetch(criteria=AND(uid=uid)))
    
            if not mails:
                return [TextContent(type="text", text=f"UID {uid}에 해당하는 메일을 찾을 수 없습니다.")]
    
            mail = mails[0]
    
            if output_format == "json":
                content = mail_to_json(mail)
            else:
                content = mail_to_text(mail, detailed=True)
    
        return [TextContent(type="text", text=content)]
  • The registration and schema definition for the 'get_mail_detail' tool.
        name="get_mail_detail",
        description="특정 메일의 상세 정보 조회",
        inputSchema={
            "type": "object",
            "properties": {
                "uid": {
                    "type": "string",
                    "description": "조회할 메일의 UID"
                },
                "format": {
                    "type": "string",
                    "enum": ["json", "text"],
                    "default": "json",
                    "description": "출력 형태 (json: JSON 형태, text: 읽기 쉬운 텍스트(내용은 없음))"
                }
            },
            "required": ["uid"],
        }
    ),
Behavior2/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. While '조회' implies a read-only operation, the description doesn't specify authentication requirements, rate limits, error conditions, or what constitutes '상세 정보' (detailed information). For a tool with no annotation coverage, this leaves significant behavioral questions unanswered.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information. Every word earns its place in conveying the core function.

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 mail retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what '상세 정보' includes (headers, body, attachments, metadata), doesn't mention authentication requirements, and provides no context about the mail system or data format. With siblings that handle mail operations, more context about this tool's specific role 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?

With 100% schema description coverage, the schema already fully documents both parameters (uid and format with enum values). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain uid format requirements, provide format selection guidance, or clarify the 'text' format limitation mentioned in the schema ('내용은 없음' - no content).

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 verb ('조회' - retrieve/view) and resource ('특정 메일의 상세 정보' - specific mail's detailed information), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from similar siblings like 'list_mails' or 'list_mails_paginated' which might also provide mail information but in list format rather than detailed view.

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. With siblings like 'list_mails' and 'list_mails_paginated' that also retrieve mail information, there's no indication that this tool is for detailed single-mail retrieval versus list-based retrieval. No prerequisites, exclusions, or comparison context is provided.

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/Leonamin/NaverMail-MCP-Server'

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