Skip to main content
Glama
mail-mcp-server

mail-mcp-server

execute_plan

Apply a previously dry-run, user-approved email plan exactly as previewed. Use it to run single-use plans that change or organize mail after the user confirms the summary.

Instructions

Runs a plan made by any plan_* tool, on exactly what its dry run showed. Never call this without the user's explicit yes for this plan, given after they saw its summary. Plans are single-use and expire after 10 minutes.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "execute_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the key traits: this is a committing, irreversible execution gated on user consent, plans are single-use, and they expire after 10 minutes. It still leaves open failure behavior (partial execution, errors) and whether the operation is idempotent.

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?

Three tightly packed sentences: what it does, the consent gate, and the lifetime constraint. The consent guard is front-loaded and nothing is redundant.

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 single-parameter mutation tool with no annotations and no output schema, the definition covers consent gating, dry-run fidelity, and plan lifetime. Return value and post-failure state are unaddressed, but the essentials for correct invocation are present.

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 0% on the single plan_id parameter, so the description must compensate. It does so indirectly by locating plan_id's origin (output of any plan_* tool) and its 10-minute validity window, but adds no format or validity details beyond that.

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 (Runs) and resource (a plan made by any plan_* tool) and pins the scope with "on exactly what its dry run showed." An agent can distinguish this execution step from the plan_* siblings that only create plans.

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?

Gives an explicit precondition — the user's explicit yes, given after seeing the plan summary — and the "Never call this without..." phrasing works as a clear exclusion. It does not say what to do when a plan has expired (re-plan vs. retry), which would make it a 5.

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