Skip to main content
Glama
agentisend

agentisend

Move an email to a new time

reschedule_email
Idempotent

Move a scheduled or canceled message to a new send time; sent or failed emails are refused by status.

Instructions

Purpose: move a scheduled — or canceled — message to a new send time. NOT for: a settled message. Sent, bounced, failed, complained and suppressed cannot be moved, and the refusal names the status. Returns: the message id, its status and the new scheduled time.

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": {
      "email_id": "<email_id>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "reschedule_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesThe message id returned by send_email.
timezoneNoTime zone for a scheduled_at phrase such as "tomorrow 9am". An ISO time ignores this. Example: America/Los_Angeles. Omitted phrases are read in UTC.
scheduled_atYesThe same field PATCH /emails/:id takes: ISO 8601 ("2026-09-05T09:00:00Z") or a short phrase ("in 1 hour", "tomorrow 9am", "friday 14:00"), within the next 30 days. "now" sends it straight away; a time in the past is refused.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
statusNo
scheduled_atNoISO 8601 time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so safety and repeatability are covered structurally. The description contributes the failure-mode detail (refusal identifies the offending status) and the return payload, but says nothing about permissions, side effects on the existing schedule, or rate limits beyond what the schema already states.

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 labeled lines — purpose, exclusion, returns — with no filler, and the core purpose is front-loaded in the first sentence. Every sentence carries distinct information.

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?

An output schema exists, so the brief return summary is supplementary rather than load-bearing. Combined with rich annotations and full schema coverage, the definition covers what an agent needs to call it correctly; only cross-tool routing advice for settled messages is absent.

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 description coverage is 100%, with the schema itself explaining timezone resolution, ISO vs. phrase formats, the 30-day window, and the idempotency key. The description adds no parameter-level meaning, so the baseline 3 applies.

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 (move) and resource (a message) plus the exact state scope: scheduled or canceled. The 'NOT for: a settled message' clause enumerates the excluded statuses, so an agent can immediately separate this from send_email or cancel_email without inspecting schemas.

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?

The 'NOT for' line gives an explicit exclusion list (sent, bounced, failed, complained, suppressed) and notes that the refusal names the status, which is actionable. It stops short of naming the alternative tool an agent should reach for when the message is settled, which keeps it from a 5.

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