Skip to main content
Glama

Create Forward Draft

create_forward_draft

Creates a forward draft in the Drafts folder with the original message quoted underneath, so you can review it before sending.

Instructions

Create a forward draft in the Drafts folder 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>",
      "to": "<to>"
    },
    "name": "create_forward_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient email address(es), comma-separated for multiple
commentNoOptional note 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 forward

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?

The annotations already declare a non-read-only, non-destructive write; the description adds useful behavioral detail that the result is a draft in Drafts, the original is quoted underneath, and nothing is sent until send_draft is called. That clarifies the side effect and review-before-send workflow beyond annotations. It does not cover permissions, error behavior, or return/reference details, but the safety profile is already carried by annotations.

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?

The definition is two short sentences, front-loading the action and outcome before the follow-up instruction. Every phrase contributes to purpose or next step, with no filler. Structure is efficient and easy to parse.

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 4-parameter tool with full schema coverage and annotations covering the safety profile, the description supplies the core purpose and review-then-send workflow. It does not mention what the tool returns (e.g., a draft identifier) or error/edge cases, which would help an agent chain to send_draft. That is a minor gap, so it is complete enough to call but not fully 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%, and the schema already defines message_id, to, comment, and mailbox, including the meaning of comment and delegated mailbox. The description adds no parameter-level syntax or constraints beyond the schema. Therefore it meets the baseline for fully documented parameters but does not add extra semantic value.

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 states a specific verb+resource ('Create a forward draft') and scope ('in the Drafts folder with the original quoted underneath'), making the outcome concrete. It also names the follow-up sibling send_draft, so the agent can distinguish this draft-creation step from sending. The only minor gap is that it doesn't explicitly contrast with create_draft or send_forward, but 'forward draft' is specific enough.

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 gives clear context: create the draft first, review it, then call send_draft. This tells the agent the intended workflow and when this step applies. It stops short of explicit when-not guidance, such as directing immediate sends to send_forward or distinguishing from other draft-creation siblings, so it 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