Skip to main content
Glama
korean-mail-mcp

korean-mail-mcp

by cpa333

download_attachment

Saves an email attachment to a PC and returns its full path. Uses the Downloads folder by default, creates missing folders, and directs you to read the saved file from that path.

Instructions

첨부 파일을 PC에 저장하고 전체 경로를 돌려준다. save_dir가 없으면 다운로드 폴더에 저장하고, 폴더가 없으면 만든다. 파일 내용은 돌려주지 않으니 경로로 직접 읽는다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>",
      "index": "<index>"
    },
    "name": "download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYessearch_emails가 돌려준 uid
indexYesread_email 첨부 목록의 번호
folderYes메일함 경로. list_folders의 path 값
accountYes메일 계정의 메일 주소. 설정된 계정이 없다. 어느 계정인지 요청에서 분명하지 않으면 도구를 부르기 전에 사용자에게 묻는다.
save_dirNo저장할 폴더의 절대 경로

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the default save location, that missing folders are created, and that file contents are not returned. It omits what happens on filename collision (overwrite vs. rename) and any permission or error behavior, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and return value, then the default behavior, then the caveat about contents. Every sentence adds information and none repeats the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write-side tool with no annotations and no output schema, the description covers the essential contract: what is written, where, the default, and what is returned. The main remaining gap is collision/overwrite behavior, which matters for a file-writing tool but is a secondary concern.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining save_dir's default (Downloads folder) and the folder-creation side effect. The other four parameters are left entirely to the schema, which already documents them well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('첨부 파일을 PC에 저장') and adds the return contract ('전체 경로를 돌려준다'), which lets an agent distinguish it from read_email, whose attachment list only supplies the index. Nothing about the purpose is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a fallback rule for when save_dir is omitted and tells the agent to read the file via the returned path rather than expecting contents. However, it never states when to prefer this tool over siblings or what to do when a download is unnecessary, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.