Skip to main content
Glama
mail-mcp-server

mail-mcp-server

list_mailboxes

Lists mailboxes connected to the server and shows the status of each mailbox's last connection.

Instructions

The mailboxes this server holds a token for, and how the last connect ended.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/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 only that results are scoped to mailboxes with a stored token plus some connect outcome. It says nothing about read-only nature, whether it performs network/authentication work, or what 'how the last connect ended' actually contains.

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 filler, but it is a fragment rather than a front-loaded statement of purpose, and the phrase 'how the last connect ended' is cryptic at first read.

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

Completeness2/5

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

With no output schema and no annotations, the description is the only source of return-value information, and it is too terse to convey the shape of the response—what identifies a mailbox, or whether connect status is a boolean, timestamp, or error string. For a zero-parameter discovery tool this leaves real ambiguity.

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 clarify beyond the schema; baseline 4 applies. The sentence correctly implies no input is needed to enumerate the held mailboxes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (mailboxes the server holds a token for) and an added datum (how the last connect ended), but it is a noun-phrase fragment with no verb, so the action remains implicit from the name. An agent can infer it is a listing tool, though it is not explicitly distinguished from siblings such as mailbox_overview or connect.

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 guidance on when to call this versus connect or mailbox_overview, no prerequisites, and no exclusions. The agent must infer from the name alone that this is a starting-point/discovery call.

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