Skip to main content
Glama
owlpost

owlpost

reply_email

Sends a reply to an existing email after confirmation, preserving thread headers and quoting the original body; supports reply-all, HTML, and attachments.

Instructions

Reply to a message and send the reply immediately; confirm with the user first.

Addresses the reply to the original sender (plus the original To/Cc, minus your own address, when reply_all is true), prefixes the subject with "Re:" if needed, sets In-Reply-To and References so clients thread it correctly, and quotes the original plain-text body below yours.

Args: account: Account name from list_accounts. folder: Folder containing the message being answered. uid: UID of the message being answered. body: Your reply text; the quoted original is appended after it. reply_all: Also reply to the original To and Cc recipients. html: Optional HTML alternative for the reply. attachments: Local file paths to attach.

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>",
      "folder": "<folder>",
      "uid": "<uid>",
      "body": "<body>"
    },
    "name": "reply_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
bodyYes
htmlNo
folderYes
accountYes
reply_allNo
attachmentsNo

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.7/5.0
Behavior5/5

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

Annotations only declare the generic profile (readOnly=false, destructive=false, openWorld=true, idempotent=false); the description adds the substantive behavior an agent needs — the reply is sent immediately and is not reversible, user confirmation is required first, and the exact addressing/threading/quoting transformations applied are spelled out.

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?

Front-loaded imperative sentence carrying the critical safety constraint, followed by a compact behavior paragraph and a clean Args list; no filler and every clause conveys either a constraint or an observable effect.

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 7-parameter mutation tool with an output schema present, the definition covers invocation prerequisites, side effects, addressing rules, and per-parameter meaning; nothing an agent needs to call 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?

With 0% schema description coverage, the description carries the full burden and does document all seven parameters, adding real meaning for body (quoted original appended), reply_all (includes original To/Cc), html (alternative part), attachments (local file paths), and account (sourced from list_accounts). The folder and uid entries are largely restatements of the field names, so it falls just short of complete.

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?

Opens with a specific verb+resource ("Reply to a message and send the reply immediately") and immediately distinguishes itself from send_email/forward_email by describing reply-specific mechanics: Re: prefixing, In-Reply-To/References headers, and quoting the original body.

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?

Gives a concrete procedural constraint ("confirm with the user first") that governs when/how to invoke it, and the reply_to-an-existing-message framing implicitly excludes composing new mail. It stops short of explicitly naming send_email/forward_email as the alternatives for those cases.

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