Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_analysis_spam

Run spam analysis on an email message to determine its spam score and classification.

Instructions

Run spam analysis for a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYes

Implementation Reference

  • src/index.ts:386-396 (registration)
    Registration of the 'mailosaur_analysis_spam' tool via server.tool() with a Zod schema requiring messageId (string) and a handler that calls mailosaur.analysis.spam(messageId).
    server.tool(
      "mailosaur_analysis_spam",
      "Run spam analysis for a message.",
      {
        messageId: z.string()
      },
      async ({ messageId }) => {
        const result = await mailosaur.analysis.spam(messageId);
        return response(result);
      }
    );
  • Handler function for the spam analysis tool. It calls mailosaur.analysis.spam(messageId) and returns the result via the response() helper.
    async ({ messageId }) => {
      const result = await mailosaur.analysis.spam(messageId);
      return response(result);
    }
  • Input schema for the tool, requiring a single 'messageId' string parameter.
    {
      messageId: z.string()
    },
  • The response() helper used to wrap the spam analysis result in MCP content format (JSON-stringified 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 are present, so the description carries full burden. It fails to disclose whether the analysis is read-only, what permissions are needed, or what side effects (e.g., marking the message). The term 'analysis' implies no modification, but this is not explicit.

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

Conciseness2/5

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

The description is a single sentence that is too minimal. It achieves brevity at the expense of essential detail. Important information about the parameter, return value, and behavior are omitted.

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

Completeness2/5

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

Given there is no output schema and only one parameter, the description does not explain what the tool returns (e.g., spam score, boolean, classification). The agent lacks critical information to interpret the result and decide on further actions.

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?

Schema description coverage is 0%, yet the description adds no meaning to the 'messageId' parameter beyond the schema. It does not explain what constitutes a valid message ID or how to obtain one. The description should compensate for the missing schema descriptions.

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 tool runs spam analysis for a message. The verb 'Run' and resource 'spam analysis' are specific. However, it does not distinguish from the sibling 'mailosaur_analysis_deliverability' which might perform a related but different analysis.

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 usage guidance is provided. The description does not indicate when to use this tool, when not to use it, or mention any alternatives. The agent has no context to decide between spam and deliverability analysis.

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