Skip to main content
Glama
mail-mcp-server

mail-mcp-server

list_forwarding

Retrieve a mailbox's forwarding addresses, their confirmation status, and the auto-forward setting to verify where messages are redirected.

Instructions

Forwarding addresses (with confirmation status) and the auto-forward setting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mailbox": "<mailbox>"
    },
    "name": "list_forwarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/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 behavioral burden, and it discloses almost nothing: not that this is a read-only operation, not what permissions or mailbox scopes are required, not whether results are paginated, and not the shape of any return value. The only behavioral hint is the parenthetical that confirmation status is included per address.

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 fragment with no filler, but it is not front-loaded with an action verb and reads as a return-value label rather than a task statement. It is concise at the cost of completeness rather than concise and complete.

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?

The tool itself is simple (one required parameter), which lowers the bar, but with no annotations and no output schema the description is the only source of truth about what this returns and how it behaves, and it supplies a phrase rather than an explanation. It does not tell an agent whether the auto-forward setting is a boolean or a full configuration object, nor how failures surface.

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?

Only one parameter (mailbox) exists and it is fully documented in the schema (100% coverage), including a pointer to list_mailboxes. The description adds no meaning beyond that, so the high-coverage baseline of 3 applies. A note on whether mailbox must be a connected account of the same user would have raised this.

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 is a noun phrase ("Forwarding addresses ... and the auto-forward setting") with no verb, so the agent must infer from the name that this is a read/list operation. It does identify the two things returned (forwarding addresses with confirmation status, and the auto-forward setting), which is more specific than a tautology, but it never states the action.

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 guidance at all, and no mention of related siblings such as plan_add_forwarding_address or plan_set_auto_forward, which an agent would plausibly confuse with this read tool. The parenthetical "see list_mailboxes" lives in the schema, not the description, so routing guidance is effectively absent.

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