Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_messages_reply

Reply to an email message by specifying its ID and providing the response body, including text, HTML, attachments, and CC recipients.

Instructions

Reply to an email message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMessage ID.
bodyYes

Implementation Reference

  • The handler function for mailosaur_messages_reply. It calls mailosaur.messages.reply(id, body) and returns the result JSON-stringified.
    async ({ id, body }) => {
      const result = await mailosaur.messages.reply(id, body);
      return response(result);
    }
  • MessageBodySchema used as the 'body' parameter schema. Defines cc, text, html, and attachments fields.
    const MessageBodySchema = z.object({
      cc: z.string().optional(),
      text: z.string().optional(),
      html: z.string().optional(),
      attachments: z.array(AttachmentSchema).optional()
    });
  • AttachmentSchema used by MessageBodySchema for the attachments array.
    const AttachmentSchema = z.object({
      id: z.string(),
      contentType: z.string().optional(),
      fileName: z.string().optional(),
      content: z.string().optional(),
      contentId: z.string().optional()
    });
  • src/index.ts:211-222 (registration)
    Registration of the 'mailosaur_messages_reply' tool using server.tool() with name, description, input schema, and handler.
    server.tool(
      "mailosaur_messages_reply",
      "Reply to an email message.",
      {
        id: z.string().describe("Message ID."),
        body: MessageBodySchema
      },
      async ({ id, body }) => {
        const result = await mailosaur.messages.reply(id, body);
        return response(result);
      }
    );
Behavior1/5

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

No annotations are provided, and the description gives no behavioral details beyond 'reply'. It does not disclose whether the reply is sent, if authentication is required, or how the original message is affected.

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 very concise at five words, which is efficient but may be too sparse for a tool with a nested body parameter. It is not structured in a helpful way, but it avoids verbosity.

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 the lack of annotations and output schema, the description is severely incomplete. It does not explain the reply behavior, the required structure of the body, or what the tool returns.

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 adds no meaning to the parameters beyond what the input schema provides. Schema coverage is 50% (only 'id' has a description), and the description does not compensate for the missing explanation of the nested 'body' object.

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?

The description clearly states the verb 'reply' and the resource 'email message', making the action understandable. However, it does not distinguish itself from sibling tools like 'mailosaur_messages_forward' or 'mailosaur_messages_create', which have similar actions.

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?

No guidance is provided on when to use this tool versus alternatives like forwarding or creating. There are no prerequisites or conditions mentioned, such as requiring the original message to exist.

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