Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25

reply_email

Reply to an existing email, automatically including threading headers for proper conversation continuity. Optionally save as a draft instead of sending.

Instructions

Reply to an existing email with proper threading headers (In-Reply-To, References). Automatically fetches the original email to build the reply chain. By default sends immediately; set send=false to save as a draft instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC email addresses (optional)
toNoRecipient email addresses (optional, defaults to the original sender)
bccNoBCC email addresses (optional)
fromNoSender email address (optional, defaults to account primary email)
sendNoWhether to send the reply immediately (default: true). Set to false to save as draft instead.
replyToNoReply-To email addresses (replies go here instead of to the sender)
htmlBodyNoHTML body (optional)
textBodyNoPlain text body (optional)
originalEmailIdYesID of the email to reply to
Behavior3/5

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

Discloses key behaviors like threading and draft saving, but lacks details on error scenarios, permissions, or side effects, which is notable given no 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 focused sentences, no fluff, front-loaded with the core action.

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 essential behavior but omits output format and error handling; acceptable for a reply function with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema by explaining default sending behavior and that 'to' defaults to original sender; schema coverage is 100% so baseline is met with added 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?

Clearly states it replies to an existing email with threading headers, distinguishing from sending new emails or creating standalone drafts.

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?

Provides clear context on when to use (reply to existing email) and the option to save as draft via send parameter, but does not explicitly mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MadLlama25/fastmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server