Skip to main content
Glama

reply

Destructive

Compose and send a plain-text email response with the quoted original, or save it as a draft unless confirm is true; opens Mail hidden if needed.

Instructions

Reply to a message with plain text. Mail adds the quoted original. Without 'confirm' true nothing is sent: the message is saved as a draft. If Mail is not running, applesauce opens it hidden in the background and leaves it open.

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage id from search_mail.
bodyYesPlain text of the reply.
confirmNoMust be true to send.
reply_allNotrue to reply to all recipients. Default false.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the crucial draft fallback semantics, that the quoted original is added automatically, and that Mail is launched hidden and left open if not running. These are non-obvious side effects and permission-adjacent behaviors that an agent could not derive from the structured fields, and they are consistent with the destructive hint rather than contradicting it.

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 short sentences, each carrying distinct information: action, quoting behavior, send-versus-draft safety rule, and runtime side effect. The most important safety constraint is front-loaded right after the action statement, and there is no filler.

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?

For a six-parameter, side-effecting mail tool with no output schema, the definition covers the risk profile, the automatic quoting, and the background-launch behavior well. It does not indicate what the call returns (draft identifier, sent message, or nothing), which is a modest gap given the absence of an output schema.

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 100%, so the baseline is 3, but the description adds genuine meaning to 'confirm' by explaining the consequence of omission (a draft is saved, nothing sent) rather than just restating 'Must be true to send.' The other parameters, reply_all, in_account and in_mailbox, are left entirely to the schema, which is acceptable but keeps this from a 5.

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 first sentence gives a specific verb and resource: 'Reply to a message with plain text,' and the follow-up clarifies that Mail appends the quoted original, which distinguishes it from a bare send or draft tool. It never names siblings like forward_message or create_draft explicitly, so an agent must infer the boundary rather than read it.

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 definition gives a clear conditional rule for the send path ('Without confirm true nothing is sent'), which is exactly the context an agent needs before invoking a mail-mutating tool. It stops short of routing advice against alternatives such as create_draft or forward_message, so the 'when to use this instead' dimension is only partially covered.

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