Skip to main content
Glama
codefuturist

Email MCP Server

by codefuturist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Forward email

forward_email

Send an existing email to new recipients with an optional note, preserving the original text as a quote and reattaching attachments.

Instructions

Forward an email to new recipients with optional additional message. The original is converted to readable text and "> "-quoted below your note; its attachments are re-attached unless includeAttachments is false. Set html=true to also send an HTML part carrying the original HTML in a blockquote.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipients
toYesForward to these recipients
bodyNoAdditional message above the forwarded content
htmlNoAlso send an HTML part with the original HTML preserved in a blockquote (default: false — text only)
accountYesAccount name from list_accounts
emailIdYesEmail ID to forward (from list_emails or get_email)
mailboxNoMailbox where the original email isINBOX
includeAttachmentsNoRe-attach the original attachments (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / cc / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • addedInput schema / properties / html
      Added value: +{
+  "default": false,
+  "description": "Also send an HTML part with the original HTML preserved in a blockquote (default: false — text only)",
+  "type": "boolean"
+}
    • addedInput schema / properties / includeAttachments
      Added value: +{
+  "default": true,
+  "description": "Re-attach the original attachments (default: true)",
+  "type": "boolean"
+}
    • changedInput schema / properties / to / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv0.2.3

TDQS

A4/5.0
Behavior4/5

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

Annotations cover safety (destructiveHint=false, readOnlyHint=false, openWorldHint=true), so the description correctly focuses on mechanics: how the original is quoted, attachment re-attachment, and the html flag's effect. It omits any delivery-failure or rate-limit context but adds substantive transformation details beyond 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?

Three tight sentences, front-loaded with the core action, then the transformation rule, then the html opt-in. 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?

Covers the key behavioral surprises (quote wrapping, attachment default, html toggle) that an agent couldn't infer from the name alone. No output schema exists, but this tool realistically returns only send status, and no usage exclusions are stated — a minor gap.

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 html and includeAttachments. The description reinforces html and includeAttachments semantics but adds no format/syntax guidance beyond what the schema provides. Baseline 3 is appropriate.

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 (Forward) and resource (email) with the key transformation described — original converted to quoted text with attachments re-attached. Clearly distinguishable from siblings like send_email (new message) and reply_email (to original sender).

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 implicitly signals when to use this over send_email/reply_email by describing forwarding semantics, but never explicitly names alternatives or states when-not-to-use. Guidance is implied through behavior rather than stated.

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