Skip to main content
Glama

List mailboxes

list_accounts
Read-onlyIdempotent

Lists available mailboxes and their aliases, addresses, status, allowed actions, and temporary access expiry so agents can choose the correct account before using other mailbox tools.

Instructions

List the mailboxes this connection may use, with alias, address, status and allowed actions. Call it first: every other tool takes one of these aliases as account. Rights that were granted only for a limited time are listed under temporary, each with its expires_at. IMAP mailboxes you can draft in also list from_addresses (the mailbox address and its send-as aliases).

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

Output Schema

NameRequiredDescriptionDefault
accountsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds meaningful behavior beyond them: temporary rights appear under "temporary" with `expires_at`, and IMAP mailboxes that allow drafting include `from_addresses` with the mailbox address and send-as aliases.

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?

Four sentences, front-loaded with the core purpose and prerequisite. Each sentence adds distinct value: returned fields, required call ordering, temporary-rights semantics, and IMAP from_addresses behavior.

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

Completeness5/5

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

The definition is complete for a parameterless discovery tool with a full output schema and annotations already covering safety. It additionally explains prerequisite ordering and special output cases (temporary rights, IMAP from_addresses) that an agent needs in order to use the tool correctly.

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 has zero parameters, so there is no parameter semantics to explain, which sets the baseline at 4. The description mentions the `account` alias used by sibling tools but does not need to document input parameters for this tool.

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?

States a specific verb and resource ("List the mailboxes") and enumerates the returned fields (alias, address, status, allowed actions). It also clarifies scope ("this connection may use") and distinguishes the tool as the entry point every other tool depends on.

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

Usage Guidelines5/5

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

Gives explicit sequencing guidance: "Call it first: every other tool takes one of these aliases as `account`." That tells an agent both when to use it and why it must precede other calls, leaving no ambiguity.

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