Skip to main content
Glama

Mail List Mailboxes

mail_list_mailboxes

List Apple Mail mailboxes across all accounts or filter by a specific account to inspect available folders.

Instructions

List mailboxes, optionally for one account.

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_mailboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo

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 provided, so the description carries the full burden. It implies a read-only listing operation and a default scope of all mailboxes, but does not mention permissions, pagination, ordering, or what is returned. These gaps are significant for a tool with no annotation coverage.

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 definition is a single well-formed sentence with no wasted wording. The core operation is front-loaded, followed immediately by the only optional constraint.

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 simple one-parameter list tool with no output schema, the description covers the core action and the optional filter. However, with no annotations and no return schema, it leaves out basic operational context such as whether listing is paginated or what happens when the account is omitted.

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?

Schema description coverage is 0%, so the description must compensate for the lone account parameter. It usefully explains that the parameter is optional and scopes the listing to one account, but it does not specify whether the value is an account ID, email address, or another identifier format.

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: 'List mailboxes.' It also clarifies the optional scoping by account. It does not explicitly distinguish itself from siblings such as mail_list_accounts, but the resource wording makes the intent understandable.

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 phrase 'optionally for one account' implies that omitting the parameter lists all mailboxes, but the description gives no guidance on when to use this tool versus alternatives or when the account filter is appropriate. Usage is only implied, not instructed.

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