Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_forward

Forward the last message in a conversation, or a chosen message with attachments, to new recipients; requires confirm=true and verifies send state to avoid duplicate sends.

Instructions

Forward the last message of a conversation, or message_index (with its attachments), to new recipients.

Send is never repeated blind: when Gmail's reaction to Send is unclear the mail is looked up in Outbox / Sent; if that cannot tell, the op fails with error 'send_state_unknown' and nothing is re-sent (check gmail.list folder='sent' before any retry). A result may carry verified_in='outbox' | 'sent' when the send was confirmed that way.

Requires confirm=true (outward-facing or destructive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gmail_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoAdditional Cc recipients.
toNoAdditional To recipients.
bccNoAdditional Bcc recipients.
bodyNoText written above the quoted message (any Unicode, newlines allowed).
indexNoRow index of the conversation (from gmail.list / gmail.search); omit to use the conversation already open.
queryNoRun this Gmail search first and take `index` from its results.
folderNoOpen this folder/label first and take `index` from it.
confirmNoMust be true: this action is outward-facing or destructive.
draft_onlyNoSave the reply as a draft instead of sending it.
attachmentsNoPaths of files on this computer to attach.
drive_filesNoGoogle Drive files to insert as links: 'name' (found with Drive search) or '/Folder/name' (from My Drive).
message_indexNoAnswer this message of the thread (0 = oldest, numbering of gmail.read) through its own header actions; default: the last message.
expect_subjectNoSafety check: the conversation's subject must contain this text (case-insensitive), otherwise nothing is sent (not_found).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that send is verified against Outbox/Sent, that an unclear state fails with 'send_state_unknown' without re-sending, and that verified_in may appear on the result. It does not state that forwarding is irreversible once sent, nor what happens when confirm is false beyond 'must be true'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and scope are front-loaded into the first sentence, and the send-verification paragraph is dense but each sentence carries operational consequence. The confirm requirement is tacked on as a final line rather than integrated, a minor structural inefficiency.

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 13-parameter mutation tool with no annotations and no output schema, the description covers the highest-risk behavior (duplicate-send avoidance, confirm gate, error signal) and names the verification field on results. The lower-risk parameters (drive_files, attachments, expect_subject, draft_only) are left entirely to the 100%-covered schema, which is acceptable but means the description alone would not fully prepare an agent.

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 every one of the 13 parameters is already documented. The description adds a little framing ('with its attachments', 'to new recipients') and restates the message_index default, but adds no syntax, format, or interaction detail beyond what the schema properties already say. 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 ('Forward the last message of a conversation... to new recipients') and identifies the message_index variant, which implicitly separates it from gmail_reply/gmail_reply_all since the target is new recipients rather than the sender. It never names an alternative sibling outright, so sibling differentiation is inferred 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?

The description does establish a hard precondition (confirm=true) and gives retry guidance ('check gmail.list folder='sent' before any retry'), which is real usage direction. It never says when to choose forward over gmail_reply, gmail_reply_all, gmail_send, or gmail_draft, and the draft_only escape hatch is only visible in the schema.

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