Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_servers_create

Create a Mailosaur server to enable email and SMS testing. Provide the server name to configure it.

Instructions

Create a Mailosaur server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • src/index.ts:262-271 (registration)
    Registration of the mailosaur_servers_create tool using server.tool(). Defines name, description, schema (name: z.string()), and handler.
    server.tool(
      "mailosaur_servers_create",
      "Create a Mailosaur server.",
      {
        name: z.string()
      },
      async ({ name }) => {
        const result = await mailosaur.servers.create({ name });
        return response(result);
      }
  • Handler function for the mailosaur_servers_create tool. Accepts a 'name' string and calls mailosaur.servers.create().
    async ({ name }) => {
      const result = await mailosaur.servers.create({ name });
      return response(result);
    }
  • Input schema for mailosaur_servers_create: expects a single required string field 'name'.
    {
      name: z.string()
    },
  • The response() helper function used to format the tool's return value as JSON 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?

With no annotations, the description should disclose behavioral traits like side effects or permissions. It only states 'Create a Mailosaur server,' implying resource creation but not confirming whether it's idempotent, requires authentication, or has any limits.

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 four words, but conciseness comes at the cost of completeness. It is not overly verbose, yet it fails to provide necessary information for correct use.

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 the simplicity of the tool (1 param, no output schema), the description is incomplete. It does not explain the return value, side effects, or the role of a Mailosaur server, leaving the agent with insufficient context for reliable invocation.

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 sole parameter 'name' has no description in the schema (0% coverage), and the tool description does not clarify its semantics (e.g., unique, display name, format). The description adds no value beyond the schema's existence of the parameter.

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 action ('Create') and the resource ('a Mailosaur server'), which is specific and distinguishes from sibling tools like mailosaur_servers_delete or mailosaur_servers_get. However, it lacks additional context about what creating a server entails or returns.

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 guidelines are provided. The description does not indicate when to use this tool (e.g., initial setup) or when not to use it (e.g., if a server already exists). Alternatives among siblings are not mentioned.

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