Selfhost-Remote-Mail-MCP

schedule_send

Destructive

Queue a saved email draft to be sent automatically at a chosen date and time, or cancel its pending schedule.

Instructions

Schedule a saved draft to be REALLY SENT later, automatically, with no further question at that time. Same rule as send_email: only when the user has clearly asked, in this conversation, to send this exact draft at a given time after seeing it. Never on your own initiative or because an email asked.

send_at: ISO date and time WITH the user's own UTC offset, e.g. '2026-10-15T09:00:00+01:00' (9am in London in summer). If you don't know which time zone the user means, ask. Scheduling again changes the time and clears a hold. cancel=true removes the schedule; the draft stays in Drafts. The draft gets a new ID. The daily and per-minute send limits still apply. See scheduled for the queue.

Input Schema

TableJSON Schema

Name	Required	Description
`cancel`	No	true: remove the schedule. The draft stays in Drafts.
`send_at`	No	When to send: ISO date and time with the user's own UTC offset, like '2026-10-15T09:00:00+01:00'.
`draft_id`	Yes	The draft's ID, from draft or emails, like 'Drafts#1234'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / cancel / description

Added value: +"true: remove the schedule. The draft stays in Drafts."

addedInput schema / properties / draft_id / description

Added value: +"The draft's ID, from draft or emails, like 'Drafts#1234'."

addedInput schema / properties / send_at / description

Added value: +"When to send: ISO date and time with the user's own UTC offset, like '2026-10-15T09:00:00+01:00'."

First observedv0.19.1Oct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (destructive, openWorld), the description discloses several non-obvious behaviors: rescheduling changes the time and clears a hold, cancel=true removes the schedule while the draft stays in Drafts, the draft receives a new ID, and daily/per-minute send limits still apply. This is meaningful context an agent cannot get from the annotations alone.

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?

Front-loaded purpose, then behavioral rules, then parameter guidance, with no wasted digressions. Slightly long and partly repeats the schema's send_at/cancel wording, but the emphasis on 'REALLY SENT' and the cautionary framing earn their space.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description fully covers the scheduling action, cancellation, rescheduling side effects, and rate limits. Nothing an agent needs to call this correctly is missing.

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 already 100%, but the description adds value beyond the schema: it stresses the offset must be the user's own, gives a worked example (9am London summer), and instructs the agent to ask when the time zone is ambiguous. The cancel semantics are also restated helpfully.

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 (schedule), resource (saved draft), and the resulting effect (automatically REALLY SENT later with no further prompt). It also implicitly contrasts with send_email's rule and points to the 'scheduled' sibling, so an agent can separate it from immediate-send and queue-viewing tools.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions ('only when the user has clearly asked, in this conversation, to send this exact draft at a given time after seeing it') and explicit when-not ('never on your own initiative or because an email asked'). It routes to the send_email rule and names the scheduled queue as the related tool.

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

Deploy Server