Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_servers_delete

Permanently delete a Mailosaur server and erase all messages stored within it.

Instructions

Permanently delete a Mailosaur server and all contained messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesServer ID.
confirmNo

Implementation Reference

  • src/index.ts:311-323 (registration)
    Registration of the 'mailosaur_servers_delete' tool via server.tool() with name, description, schema, and handler.
    server.tool(
      "mailosaur_servers_delete",
      "Permanently delete a Mailosaur server and all contained messages.",
      {
        id: z.string().describe("Server ID."),
        confirm: z.boolean().optional()
      },
      async ({ id, confirm }) => {
        requireConfirm(confirm, `delete server ${id}`);
        await mailosaur.servers.del(id);
        return emptyResponse("Server deleted.");
      }
    );
  • Handler function that calls requireConfirm() and mailosaur.servers.del(id), then returns emptyResponse.
    async ({ id, confirm }) => {
      requireConfirm(confirm, `delete server ${id}`);
      await mailosaur.servers.del(id);
      return emptyResponse("Server deleted.");
    }
  • Input schema with 'id' (required string) and 'confirm' (optional boolean) defined using Zod.
    {
      id: z.string().describe("Server ID."),
      confirm: z.boolean().optional()
    },
  • Helper function emptyResponse() used to return a simple success response.
    function emptyResponse(message = "OK") {
      return response({ ok: true, message });
    }
  • Helper function requireConfirm() that throws an error if confirm is falsy, used for destructive operations.
    function requireConfirm(confirm: boolean | undefined, action: string) {
      if (!confirm) {
        throw new Error(`Refusing to ${action}. Call again with confirm: true.`);
      }
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses irreversibility and the fact that messages are also deleted, but omits side effects, auth requirements, or behavior of the 'confirm' parameter.

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

Conciseness4/5

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

Single sentence is concise and front-loaded, but the lack of parameter descriptions makes it feel slightly incomplete.

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?

For a delete tool with a confirmation flag, the description is minimal. No output schema or error handling context, and the 'confirm' parameter's role is left implicit. Given sibling complexity, more detail on consequences would improve completeness.

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 coverage is 50% (only 'id' has a description). The tool description adds no parameter context. The 'confirm' parameter is completely unexplained, and baseline expectation for low coverage is higher description involvement.

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 'Permanently delete a Mailosaur server and all contained messages' clearly states the action (delete) and resource (Mailosaur server) with the specific consequence of removing all messages. It distinguishes from sibling tools like mailosaur_servers_get or mailosaur_servers_update.

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

Usage Guidelines3/5

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

The description implies use when permanent deletion is needed, but lacks explicit guidance on when to use alternatives (e.g., mailosaur_messages_delete for messages only) or prerequisites like server ownership verification.

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