Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_messages_search

Search email and SMS message summaries using filters like sender, recipient, subject, or body. Retrieve matching messages from a Mailosaur server.

Instructions

Search message summaries by sender, recipient, subject, or body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesMailosaur server ID.
criteriaYes
optionsNo

Implementation Reference

  • src/index.ts:149-161 (registration)
    Registration of the 'mailosaur_messages_search' tool via server.tool() with name, description, input schema, and handler.
    server.tool(
      "mailosaur_messages_search",
      "Search message summaries by sender, recipient, subject, or body.",
      {
        server: z.string().describe("Mailosaur server ID."),
        criteria: SearchCriteriaSchema,
        options: MessageWaitOptionsSchema.optional()
      },
      async ({ server, criteria, options }) => {
        const result = await mailosaur.messages.search(server, criteria, toSearchOptions(options));
        return response(result);
      }
    );
  • Handler function that calls mailosaur.messages.search() with server, criteria, and options, returning the result.
    async ({ server, criteria, options }) => {
      const result = await mailosaur.messages.search(server, criteria, toSearchOptions(options));
      return response(result);
    }
  • Input schema definition: server (string), criteria (SearchCriteriaSchema), options (MessageWaitOptionsSchema optional).
    {
      server: z.string().describe("Mailosaur server ID."),
      criteria: SearchCriteriaSchema,
      options: MessageWaitOptionsSchema.optional()
    },
  • Helper function toSearchOptions() used to transform options into SearchOptions format.
    function toSearchOptions(options: z.infer<typeof MessageWaitOptionsSchema> | undefined): SearchOptions | undefined {
      return parseDateOptions(options) as SearchOptions | undefined;
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It only states 'search' but does not disclose if it is read-only, pagination behavior, or how timeout/errorOnTimeout work. Behavioral traits beyond the basic action are missing.

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, concise but lacks necessary detail. It could be longer to explain parameters and usage without becoming verbose.

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?

No output schema, so description must hint at return values. 'Message summaries' is vague. It does not mention pagination, the list nature of results, or that server is required. Incomplete for a search tool with multiple parameters.

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 33% (only server described). The description adds the filterable fields (sender, recipient, subject, body) but does not cover options like match, timeout, or pagination. It partially compensates but leaves many parameters unexplained.

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 it searches message summaries by various fields. It uses a specific verb 'search' and resource 'message summaries'. However, it does not differentiate from sibling tools like 'list' which also retrieves messages.

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 on when to use this tool versus alternatives like 'list' or 'get'. The description does not specify that this is for filtered searches, while other tools may be for bulk operations.

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