Skip to main content
Glama
mail-mcp-server

mail-mcp-server

plan_add_forwarding_address

Plans adding a forwarding address to a Gmail mailbox without changing anything, returning affected details and a plan_id; Gmail then sends a confirmation link to click.

Instructions

Dry run: changes nothing. Returns what would be affected and a plan_id for execute_plan. Show the user the summary before asking whether to execute. Add an address mail can be forwarded to. Gmail emails it a confirmation link that has to be clicked first.

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>",
      "email": "<email>"
    },
    "name": "plan_add_forwarding_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the no-op dry-run behavior, the return shape (affected items plus plan_id), and the important external side effect that Gmail sends a confirmation link the user must click. It omits permission requirements and whether plan_ids expire.

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?

Four short sentences with no filler, each contributing distinct information. The ordering is slightly inverted—the behavioral guarantee precedes the statement of what the tool actually does—but nothing is wasted.

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

Completeness4/5

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

With no output schema, the description correctly explains what comes back (affected items and a plan_id). It also flags the confirmation-link prerequisite, which is the kind of non-obvious external dependency an agent would otherwise miss. Minor gaps remain around error cases.

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 coverage is 50%: mailbox is documented in the schema, while email is not. The phrase "add an address mail can be forwarded to" does imply that email is the target forwarding address, but no format or validation detail is added beyond that inference.

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 ("Add an address mail can be forwarded to") plus the crucial qualifier that this is a dry run that changes nothing, which cleanly separates it from execute_plan. An agent can tell what this produces (a plan_id) without opening the schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent: call this first, show the user the summary, then ask whether to execute via execute_plan. It does not spell out when NOT to use it versus adjacent planning siblings (e.g. plan_set_auto_forward), but the workflow condition is clear.

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