Skip to main content
Glama

Mail List Accounts

mail_list_accounts

List configured Mail accounts to identify which Apple Mail accounts are available for searching or managing messages.

Instructions

List configured Mail accounts.

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": "mail_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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: no statement that the operation is non-destructive and read-only, no indication of whether results are paginated, how many accounts are typically returned, or whether authentication/credentials are required. The verb 'List' implies a safe read, but that is inference rather than disclosure.

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 front-loaded sentence with no filler or redundancy, appropriately sized for a trivial zero-argument list operation. It is efficient, though the terseness leaves no room for the context that other dimensions penalize.

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?

Complexity is low (zero params, no nesting, no output schema), so the definition is close to sufficient for correct invocation. However, with no output schema and no annotations, the agent gets no sense of what an 'account' record contains or how to use the result, leaving a modest gap.

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 zero parameters and the schema is an empty object with additionalProperties=false, so there is no parameter meaning for the description to add. Baseline 4 applies for a parameterless tool.

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 uses a specific verb+resource pair ('List configured Mail accounts'), which is more precise than a bare name restatement and implies a read-only enumeration of account configurations. It stops short of explicitly distinguishing this from the adjacent 'mail_list_mailboxes', leaving the agent to infer that 'accounts' means configured login/identity records rather than folders.

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 or when-not-to-use guidance, and no named alternative such as mail_list_mailboxes for the folder case. The only signal is the word 'configured', which weakly hints this is a discovery/lookup tool, so the agent must infer the call context entirely.

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