Skip to main content
Glama
korean-mail-mcp

korean-mail-mcp

by cpa333

list_folders

Lists mailbox folders for a specified mail account, including paths, names, and special-use roles, so users can identify the right folder.

Instructions

계정의 메일함 목록(경로, 이름, 특수 용도)을 보여 준다.

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>"
    },
    "name": "list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes메일 계정의 메일 주소. 설정된 계정이 없다. 어느 계정인지 요청에서 분명하지 않으면 도구를 부르기 전에 사용자에게 묻는다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Shows' implies a read operation, but it does not confirm read-only semantics, whether folders across all accounts are returned, whether results are nested/hierarchical, or any rate limits. The mention of '(경로, 이름, 특수 용도)' is the only behavioral hint about the shape of results.

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?

A single short sentence with no padding, and the resource and return fields are front-loaded. It is terse rather than bloated; the brevity costs it completeness, not conciseness.

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

Completeness3/5

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

For a one-parameter listing tool with fully documented schema and no output schema, the description is minimally sufficient, and it usefully names the returned fields in place of an output schema. It stops short of telling the agent how this differs from list_accounts or what the result hierarchy looks like.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that the account must be resolved with the user when ambiguous. The description adds '계정의' (of the account) but nothing beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('메일함 목록을 보여 준다' — shows the mailbox folder list) and even names the returned fields (path, name, special purpose), so an agent knows exactly what it retrieves. It does not distinguish itself from siblings like list_accounts, which keeps it out of the 5 tier.

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?

There is no when-to-use guidance, no exclusion of alternatives (list_accounts, search_emails, read_email), and no prerequisites. The only implied usage is 'when you need folder paths', which the agent must infer from the purpose sentence alone.

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