Skip to main content
Glama

Reply to email

reply_message

Replies to a message or all recipients, automatically quoting the original below your text. Sends immediately or saves a draft and returns its ID when send is false.

Instructions

Reply (or reply-all) to a message. The original is quoted below your text. Sends immediately unless send is false, in which case a draft is saved and its ID returned.

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_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the message to reply to
bodyYesReply text (only the new part; the original is quoted automatically)
sendNoSend now (default true) or save as draft (false)
replyAllNoReply to all recipients (default false)
bodyFormatNoBody format: "text" (default) or "html"
attachmentsNoFiles to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely new context: the original is quoted automatically, sending happens immediately by default, and the draft branch returns an ID. It does not state what a successful send returns, which is the remaining gap.

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?

Two tight sentences with the core action front-loaded and the send-vs-draft branch stated second. No filler or redundancy.

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 6-parameter mutation tool with full schema coverage and no output schema, the description covers the key behavioral branches (immediate send, draft fallback with returned ID) and the auto-quoting behavior. A note on what a send returns and pointer to draft/forward alternatives would make it complete.

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 the schema already documents every parameter including send, replyAll, bodyFormat and attachment fields. The description reinforces the send/body semantics (body is only the new text) but adds little beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Reply (or reply-all) to a message"), which naturally distinguishes it from forward_message, send_message and create_draft. It does not explicitly name those siblings, so differentiation is implicit rather than stated.

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

Usage Guidelines3/5

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

Gives a clear behavioral condition for the draft path (send=false saves a draft instead of sending), which helps an agent pick the right mode. It offers no explicit guidance on when to use this versus create_draft, forward_message or send_message.

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