Skip to main content
Glama

Mail Send Message

mail_send_message

Sends an email with a recipient list, subject, and body through Apple Mail, letting an AI client compose and deliver messages locally on macOS.

Instructions

Send email (full_access safety profile required).

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

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
subjectYes
from_accountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one important fact: the call requires the full_access safety profile. However, for an irreversible outbound side effect it says nothing about delivery semantics, retries, rate limits, or whether the message is actually dispatched versus queued.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently structured, though its brevity reflects under-specification rather than disciplined editing.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the safety-profile prerequisite is captured. Still, for a mutation tool with zero annotation coverage and no parameter documentation, the definition is thinner than the complexity warrants.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate and instead adds nothing. The names 'to', 'subject', and 'body' are largely self-explanatory from the schema types, but 'from_account' with a null default (presumably the default account) is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Send email'), which is unambiguous and clearly distinct from the read/move/mark-oriented siblings. It stops short of explicitly naming how it differs from those siblings, but the purpose itself is unmistakable.

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

Usage Guidelines2/5

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

The only guidance is the parenthetical prerequisite that a 'full_access safety profile' is required, which is a permission condition rather than a when-to-use rule. Nothing explains when to send versus queue/draft, or what happens on partial failure, and no alternatives are referenced.

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