Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_messages_forward

Forward a specific email message by its ID to a verified address, including optional CC, text, or HTML.

Instructions

Forward an email message to a verified address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMessage ID.
toYes
ccNo
textNo
htmlNo

Implementation Reference

  • The handler function for the 'mailosaur_messages_forward' tool. It receives the message ID and forward options (to, cc, text, html), calls mailosaur.messages.forward() with them, and returns the result via the response helper.
    async ({ id, ...options }) => {
      const result = await mailosaur.messages.forward(id, options);
      return response(result);
    }
  • Input schema (Zod object) for the 'mailosaur_messages_forward' tool, defining the required 'id' and 'to' fields, and optional 'cc', 'text', and 'html' fields.
    {
      id: z.string().describe("Message ID."),
      to: z.string(),
      cc: z.string().optional(),
      text: z.string().optional(),
      html: z.string().optional()
  • src/index.ts:195-209 (registration)
    Registration of the 'mailosaur_messages_forward' tool on the MCP server via server.tool(), with its name, description, schema, and handler.
    server.tool(
      "mailosaur_messages_forward",
      "Forward an email message to a verified address.",
      {
        id: z.string().describe("Message ID."),
        to: z.string(),
        cc: z.string().optional(),
        text: z.string().optional(),
        html: z.string().optional()
      },
      async ({ id, ...options }) => {
        const result = await mailosaur.messages.forward(id, options);
        return response(result);
      }
    );
  • The 'response' helper function used by the handler to format the result as MCP text content.
    function response(value: unknown) {
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(value, null, 2)
          }
        ]
      };
Behavior2/5

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

No annotations exist to declare behavioral traits (e.g., readOnly, destructive). The description only states the action without disclosing side effects, permissions required, rate limits, or what happens to the original message.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. For a tool with five parameters, a more structured format (e.g., separating action from parameter details) would be helpful. It is front-loaded with the verb but too minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given five parameters, no output schema, and no annotations, the description is severely incomplete. It does not address optional parameters, the result of forwarding, or any prerequisites. The tool's complexity demands far more detail.

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

Parameters2/5

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

The description does not explain the purpose or meaning of any parameter beyond what the schema already provides (only 'id' has a schema description). With 20% schema coverage, the description should add context for 'to', 'cc', 'text', and 'html', but it fails to do so.

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 clearly states the action ('forward'), the resource ('email message'), and a condition ('to a verified address'). It distinguishes from siblings like 'reply' or 'create' by specifying forwarding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'reply' or 'create'. It mentions a 'verified address' but does not explain what that means or when not to use the tool.

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/MrNewDelhi/mailosaur-mcp'

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