Skip to main content
Glama

Create Reply Draft

create_reply_draft

Creates a reply draft to the sender in the Drafts folder, threading it into the original conversation with the quoted message so you can review it before sending.

Instructions

Create a reply draft (to the sender) 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_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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds real context on top: the draft lands in Drafts, threads into the existing conversation, and quotes the original beneath the new content — telling the agent nothing is actually sent yet. It does not mention permission or mailbox constraints for the delegated case, which keeps it from a 5.

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 earning its place: what is created, how it renders in the thread, and the next step. The action and destination are front-loaded with no filler.

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 three-parameter draft-creation tool with full schema coverage and no output schema, the description covers the outcome, threading behavior, and the send handoff. Nothing an agent needs to invoke it correctly is missing.

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 caveat — are already documented in structured fields. The description only reinforces that the comment is placed above the quoted original, adding no syntax or format detail beyond the schema.

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 draft'), scope ('to the sender'), and destination ('Drafts folder'). The parenthetical distinguishes it from the sibling create_reply_all_draft without naming it, so an agent can select correctly.

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?

'Review, then send with send_draft' gives the explicit follow-up action and names the sibling that completes the workflow. It implies the reply-to-sender-only case but does not explicitly state when to prefer create_reply_all_draft or create_draft instead, so it falls short of full routing guidance.

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