Skip to main content
Glama
owlpost

owlpost

send_email

Sends a new email over SMTP from a chosen account, saving a Sent copy when enabled and returning the Message-ID; confirm first because it cannot be undone.

Instructions

Send a new email over SMTP immediately; this cannot be undone, so confirm with the user first.

When the account has auto_save_sent enabled (needed for iCloud, whose SMTP does not keep a copy) the message is also appended to the Sent folder. Returns the generated Message-ID, recipients and the folder the copy was saved to (null if none). To answer an existing message prefer reply_email, which fills in recipients and threading for you.

Args: account: Account name from list_accounts; mail is sent from its address. to: Recipient email addresses. subject: Subject line. body: Plain-text body. cc: Cc recipient addresses. bcc: Bcc recipient addresses (delivered but never written to headers). html: Optional HTML alternative to the plain-text body. attachments: Local file paths to attach. in_reply_to: Message-ID this message replies to, for threading. references: Message-IDs of earlier messages in the thread.

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": {
      "account": "<account>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
htmlNo
accountYes
subjectYes
referencesNo
attachmentsNo
in_reply_toNo

Output Schema

NameRequiredDescriptionDefault
ccYes
toYes
bccYes
fromYes
subjectYes
warningNo
message_idYes
size_bytesYes
saved_to_folderYes
refused_recipientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bcc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Bcc",
      +      "type": "array"
      +    },
      +    "cc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Cc",
      +      "type": "array"
      +    },
      +    "from": {
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "message_id": {
      +      "title": "Message Id",
      +      "type": "string"
      +    },
      +    "refused_recipients": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Refused Recipients",
      +      "type": "array"
      +    },
      +    "saved_to_folder": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Saved To Folder"
      +    },
      +    "size_bytes": {
      +      "title": "Size Bytes",
      +      "type": "integer"
      +    },
      +    "subject": {
      +      "title": "Subject",
      +      "type": "string"
      +    },
      +    "to": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "To",
      +      "type": "array"
      +    },
      +    "warning": {
      +      "title": "Warning",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "from",
      +    "to",
      +    "cc",
      +    "bcc",
      +    "subject",
      +    "saved_to_folder",
      +    "size_bytes",
      +    "refused_recipients"
      +  ],
      +  "title": "SendResult",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it discloses the irreversible nature of the action, the conditional Sent-folder side effect tied to auto_save_sent (with the iCloud rationale), and the contents of the return value including the null case. That is meaningful context the annotations do not convey. It does not cover failure modes such as SMTP errors or attachment limits, so it stops short of the top mark.

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?

The irreversible-action warning and the sibling routing are front-loaded before the mechanical Args list, which is the right ordering for a high-stakes tool. The Args block is long but each line is short and scannable; only the subject/body entries are wasted words.

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?

For a 10-parameter, non-idempotent, open-world mutation tool, the description covers prerequisites, the confirmation requirement, the side effect on the Sent folder, and the alternative tool for replies. Return values are summarized even though an output schema exists, and nothing essential to calling it 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 description coverage is 0%, so the description must carry parameter meaning, and the Args block largely does: it explains where account values come from, that bcc addresses are never written to headers, that attachments are local file paths, and that in_reply_to/references drive threading. A few entries are near-tautological restatements ("subject: Subject line", "body: Plain-text body"), which keeps it from a 5.

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?

The opening clause names a specific verb and resource ("Send a new email over SMTP") plus an immediacy constraint, and the closing sentence explicitly separates it from reply_email, which covers the respond-to-existing-message case. An agent can distinguish this from save_draft_email, reply_email, and forward_email without inspecting 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?

It gives both a positive usage rule and an explicit alternative: "To answer an existing message prefer reply_email, which fills in recipients and threading for you." It also states a prerequisite (account name comes from list_accounts) and a required pre-action step (confirm with the user first).

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