Skip to main content
Glama

Send Email Reply

send_reply
Destructive

Replies to an email sender and sends immediately, threading the message and quoting the original. Use create_reply_draft first when you need to review before sending.

Instructions

Reply to the sender of an email and send immediately. Threads into the conversation and quotes the original. Use create_reply_draft to review before sending.

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": {
      "message_id": "<message_id>",
      "comment": "<comment>"
    },
    "name": "send_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesReply content (added above the quoted original)
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the bar is lower, but the description adds genuinely new behavioral context: the send is immediate, the message threads into the existing conversation, and the original is quoted. It stops short of describing delivery failure behavior or whether the sent copy appears in a specific folder.

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, front-loaded with the action and its side effects, ending with the alternative. Every sentence contributes: action, threading/quoting behavior, and routing to the draft variant.

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 destructive send operation with full annotation and schema coverage and no output schema, the description covers the essentials: immediate send, threading, quoting, and the draft alternative. Only minor gaps remain, such as what happens on failure or whether the sent item is retrievable afterward.

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%, so all three parameters including the delegated-mailbox rules are already documented in the schema. The description adds only indirect meaning, such as 'quotes the original' clarifying where the comment text lands relative to the quoted body. Baseline 3 is appropriate when the schema carries the parameter burden.

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 description gives a specific verb (reply to the sender) plus two distinguishing behaviors: it sends immediately, threads into the conversation, and quotes the original. 'Reply to the sender' implicitly scopes it away from send_reply_all, so an agent can distinguish the two without opening either schema.

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?

It names a concrete alternative, create_reply_draft, and the condition that selects it ('to review before sending'). That gives clear routing guidance, but there is no explicit statement of when not to use this tool (e.g., no-reply address handling or irreversible-send caution beyond the annotation).

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

Deploy Server

Other Tools