Skip to main content
Glama
mail-mcp-server

mail-mcp-server

plan_update_send_as

Plan changes to a send-as address's display name, reply-to, signature, or default status without applying them. Returns affected details and a plan_id for later execution.

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. Change a send-as address's display name, reply-to or signature, or make it the default.

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

Input Schema

NameRequiredDescriptionDefault
emailYes
mailboxYesA connected mailbox address (see list_mailboxes)
reply_toNo
signatureNoHTML signature
display_nameNo
make_defaultNo

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 burden and does well: it states the tool changes nothing, returns affected items plus a plan_id, and requires user confirmation before execution. It omits permission/auth requirements and any rate-limit or error behavior, keeping it short of a 5.

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?

The dry-run guarantee is front-loaded, followed by the return value, the user-confirmation instruction, and the scope of changes. Every sentence adds information with no waste.

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?

There is no output schema, and the description explains what is returned (affected items and a plan_id), which is the key missing piece. It is nearly complete for a six-parameter mutation-planning tool, with only auth/permission context absent.

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?

Schema coverage is only 33%, so the description must compensate, and it does by naming the four mutable fields (display name, reply-to, signature, default flag) that map to parameters. The mailbox parameter is documented in the schema, but email remains unexplained in both places.

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

Purpose4/5

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

The description names a specific verb and resource ('Change a send-as address's display name, reply-to or signature, or make it the default') and frames the tool as a dry run, which separates it from execute_plan. It does not explicitly contrast with plan_create_send_as, so sibling differentiation is only partial.

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?

It gives clear workflow guidance: run this first, show the user the summary, then ask whether to execute, and pass the plan_id to execute_plan. It lacks an explicit 'do not use for creating a new send-as' exclusion, but the when-to-use context is strong.

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