Skip to main content
Glama
korean-mail-mcp

korean-mail-mcp

by cpa333

list_accounts

Retrieves the configured mail accounts and displays each account's email address and service.

Instructions

설정된 메일 계정 목록(메일 주소, 서비스)을 보여 준다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the resource: it does not state that the operation is read-only, whether it hits the network or a local config, what happens when no accounts are configured, or whether results are ordered. For a trivial zero-parameter listing tool the risk is low, which limits the harm, but the description still adds no behavioral context.

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?

A single short sentence that front-loads the resource and appends the returned fields, with no filler, hedging, or repetition. Nothing could be removed without losing information.

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?

There is no output schema, so the description usefully names the fields an agent will receive (email address, service), which is exactly the gap it should fill for a list tool. What remains unsaid—empty-state behavior and ordering—is minor for a zero-parameter read of configured accounts.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. The mention of the returned fields (email address, service) is output information rather than parameter meaning, which is a small plus but not required here.

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 pair (showing the list of configured mail accounts) and further narrows it by naming the returned fields (email address, service). The qualifier "설정된" (configured) makes clear this returns pre-registered accounts rather than arbitrary mail data, though it does not explicitly contrast itself with sibling tools like list_folders or search_emails.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative. Usage is only implied by the purpose itself: an agent would call this to discover which accounts are configured, presumably before operations that need an account identifier. That inference is straightforward for a zero-parameter list tool but is never stated.

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