Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_devices_delete

Permanently delete a Mailosaur virtual security device by specifying its ID. Requires confirmation to prevent accidental removal.

Instructions

Permanently delete a Mailosaur virtual security device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID.
confirmNo

Implementation Reference

  • The async handler function that executes the device deletion logic. It calls requireConfirm to enforce confirmation, then calls mailosaur.devices.del(id) to perform the deletion, and returns a success response.
    async ({ id, confirm }) => {
      requireConfirm(confirm, `delete device ${id}`);
      await mailosaur.devices.del(id);
      return emptyResponse("Device deleted.");
    }
  • Input validation schema defining the 'id' (required string) and optional 'confirm' (boolean) parameters for the device delete tool.
    {
      id: z.string().describe("Device ID."),
      confirm: z.boolean().optional()
  • src/index.ts:468-480 (registration)
    Registration of the mailosaur_devices_delete tool with the MCP server via server.tool(), including its name, description, schema, and handler.
    server.tool(
      "mailosaur_devices_delete",
      "Permanently delete a Mailosaur virtual security device.",
      {
        id: z.string().describe("Device ID."),
        confirm: z.boolean().optional()
      },
      async ({ id, confirm }) => {
        requireConfirm(confirm, `delete device ${id}`);
        await mailosaur.devices.del(id);
        return emptyResponse("Device deleted.");
      }
    );
  • Helper function used by the handler to enforce that destructive operations require explicit confirmation (confirm=true).
    function requireConfirm(confirm: boolean | undefined, action: string) {
      if (!confirm) {
        throw new Error(`Refusing to ${action}. Call again with confirm: true.`);
      }
  • Helper function that formats a success response indicating the device was deleted.
    function emptyResponse(message = "OK") {
      return response({ ok: true, message });
Behavior2/5

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

With no annotations, the description carries full burden. It states 'permanently delete' indicating irreversibility, but does not disclose other traits such as required permissions, what happens to associated data, or the role of the 'confirm' parameter. Minimal behavioral context.

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?

The description is a single, concise sentence with no extraneous text. It front-loads the core action and resource. However, it could include more detail without being verbose, so it is not perfect.

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 simple delete operation with two parameters and no output schema, the description is minimal. It lacks parameter explanations, usage context, and behavioral details. While the tool is straightforward, the description leaves important gaps for an agent.

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 ('Device ID.'). The description adds no additional meaning for either parameter; notably, the 'confirm' boolean is left completely unexplained. The description does not compensate for the low schema coverage.

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 clearly states the action ('permanently delete') and the resource ('Mailosaur virtual security device'), distinguishing it from sibling tools like mailosaur_devices_create, mailosaur_devices_list, and mailosaur_devices_otp.

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, no prerequisites or conditions mentioned. The description does not help an agent decide between delete and other device 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