Skip to main content
Glama

Create Reply-All Draft

create_reply_all_draft

Create a reply-all draft in Drafts that threads into the original conversation with quoted text, so you can review it before sending.

Instructions

Create a reply-all draft (to all recipients) in the Drafts folder. Threads into the conversation with the original quoted underneath. Review, then send with send_draft.

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": "create_reply_all_draft"
  }
}

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 only declare readOnlyHint=false and destructiveHint=false, so the description earns credit for clarifying that nothing is transmitted yet and that the draft threads into the existing conversation with the original quoted beneath the reply. It still doesn't say what the call returns (e.g., a draft ID) that send_draft would need.

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 short sentences, front-loaded with the operation and scope, then the next-step routing. No redundant restatement of the title and nothing superfluous.

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 three-parameter, non-destructive draft-creation tool with a fully described schema and no output schema requirement, the definition covers purpose, threading behavior, and the send path. The only missing piece is what identifier comes back for use with send_draft.

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 coverage is 100%, so message_id, comment, and mailbox are already fully documented. The description adds only the placement of the reply content ('with the original quoted underneath'), which is useful but marginal against a schema that carries the load.

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?

States a specific verb and resource ('Create a reply-all draft') and adds the parenthetical '(to all recipients)' plus the target location ('Drafts folder'), which is exactly what separates it from a plain reply draft. An agent can pick this over create_reply_draft 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?

The closing clause 'Review, then send with send_draft' names the follow-up sibling and makes the two-step draft-then-send workflow explicit. It stops short of stating when to prefer this over send_reply_all or create_reply_draft, so the routing guidance is clear but not exhaustive.

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