Skip to main content
Glama
mail-mcp-server

mail-mcp-server

plan_delete_send_as

Generates a dry-run plan to remove a send-as address from a connected mailbox and returns affected changes plus a plan_id for execution. Review the summary before confirming.

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. Remove a send-as address.

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

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?

With no annotations, the description carries the disclosure burden and does well: it states the operation is a dry run that changes nothing, describes what is returned (affected items plus a plan_id), and mandates user confirmation before execution. It omits error behavior when the address is absent and any permission requirements.

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, front-loaded with the dry-run guarantee before the workflow instruction. Each sentence carries distinct information, though the confirmation instruction reads slightly like process boilerplate rather than tool semantics.

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?

For a two-parameter planning tool with no output schema, this covers the essentials: non-destructive behavior, the returned plan_id, and the required follow-up. Missing only edge-case behavior such as an unknown or unverified address.

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-schema, while email is not. The phrase 'remove a send-as address' implicitly identifies what email means, so the description partially compensates, but it never states the address format or how to find valid addresses.

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 ('Remove a send-as address') and immediately frames it as a dry-run planner, which distinguishes it from execute_plan and the other plan_* siblings. An agent knows exactly what this produces 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 into the two-step workflow: this tool produces a plan_id, and execute_plan performs the change, with the user shown the summary first. It does not mention preconditions such as verifying the address exists via list_send_as, which is the only remaining gap.

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