Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_devices_list

Retrieve a list of virtual security devices for TOTP testing.

Instructions

List Mailosaur virtual security devices used for TOTP testing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:433-441 (registration)
    The tool 'mailosaur_devices_list' is registered via server.tool() with an empty schema and an async handler that calls mailosaur.devices.list().
    server.tool(
      "mailosaur_devices_list",
      "List Mailosaur virtual security devices used for TOTP testing.",
      {},
      async () => {
        const result = await mailosaur.devices.list();
        return response(result);
      }
    );
  • The handler function that executes the tool logic: calls mailosaur.devices.list() and returns the result via the response() helper.
    async () => {
      const result = await mailosaur.devices.list();
      return response(result);
    }
  • The response() helper function wraps a value into the MCP content format (JSON stringified with indentation).
    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 provided, so the description carries full burden. It implies read-only nature but provides no details on pagination, sorting, or whether all devices are returned. Minimal additional behavioral information beyond 'list'.

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

Conciseness5/5

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

One short, clear sentence with no extraneous information. Every word is valuable.

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

Completeness3/5

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

For a list operation with no parameters and no output schema, the description is minimally adequate but lacks details on response format, pagination, or expected results. More context would be helpful for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, and schema description coverage is 100%. The description adds no parameter information but is not needed. Baseline is set to 4 for tools with no parameters.

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 (List), the resource (Mailosaur virtual security devices), and the context (used for TOTP testing). It distinguishes this tool from siblings like create, delete, and 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. The description does not mention prerequisites, limitations, or when to use other tools like mailosaur_devices_create or mailosaur_devices_otp.

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