Skip to main content
Glama
agentisend

agentisend

Cancel a scheduled or queued email

cancel_email
DestructiveIdempotent

Stop a scheduled or queued email before it is sent and return its message ID with the new status; use it only for unsent mail, not sent history.

Instructions

Purpose: stop a message that has not gone out yet — scheduled or still queued. NOT for: recalling sent mail. Already-sent mail is history, and the refusal names the status it is actually in. Returns: the message id and its new status. A cancel is not the end: reschedule_email can revive a canceled message.

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>"
    },
    "name": "cancel_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesThe message id returned by send_email.
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.
statusNoThe message status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds genuinely new context: the refusal names the actual message status, and a cancel is reversible via reschedule_email — useful nuance that tempers the destructiveHint for an agent weighing the call.

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 clauses (Purpose / NOT for / Returns) with the primary purpose front-loaded and zero filler. Each sentence carries distinct routing or behavioral information.

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?

Covers scope, the negative case, the alternative tool, error behavior, and reversibility; an output schema exists so return values need not be re-explained, yet the brief returns note is harmless. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%; both email_id (with UUID pattern) and idempotency_key carry full inline documentation, so the schema does the heavy lifting. The description references the message id only indirectly and adds no syntax or format detail beyond it. Baseline 3 is correct here.

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 (stop) and resource (a message that has not gone out), and explicitly delimits scope to scheduled/queued rather than sent mail. An agent can distinguish it from reply_to_email or reschedule_email without opening any schema.

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?

Explicitly gives the negative case ('NOT for: recalling sent mail') and names a concrete alternative (reschedule_email) that reverses a cancel. When-to-use and when-not-to-use are both stated rather than inferred.

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