Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_servers_list

List all Mailosaur servers to manage your email testing environments.

Instructions

List all Mailosaur servers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:252-260 (registration)
    Registration of the 'mailosaur_servers_list' tool using server.tool(). The handler calls mailosaur.servers.list() and returns the result via the response() helper.
    server.tool(
      "mailosaur_servers_list",
      "List all Mailosaur servers.",
      {},
      async () => {
        const result = await mailosaur.servers.list();
        return response(result);
      }
    );
  • The handler function for 'mailosaur_servers_list'. It awaits mailosaur.servers.list() and returns the result wrapped in a response.
    async () => {
      const result = await mailosaur.servers.list();
      return response(result);
    }
  • The input schema for 'mailosaur_servers_list' — an empty object {} meaning no input parameters.
    {},
  • The response() helper function used to format the tool's return value into MCP content (text type with JSON-stringified output).
    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 must fully disclose behavior. It only states the purpose without mentioning authentication requirements, side effects, rate limits, or that the operation is read-only. Such omissions leave the agent uninformed.

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?

The single sentence 'List all Mailosaur servers.' is concise, front-loaded, and contains no extraneous words. Every word earns its place.

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 list-all tool with no output schema, the description should at least hint at the return value (e.g., 'returns a list of server objects'). It fails to do so, leaving the agent to guess the response structure. Given the low complexity, this is a significant gap.

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?

Since input schema has no parameters (coverage 100% trivially), baseline is 4. The description adds no param details, but none are needed. It correctly implies the operation's scope.

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?

Description uses specific verb 'List' and resource 'Mailosaur servers', with 'all' clearly distinguishing from sibling tools like get, create, or delete. It immediately conveys the tool's function.

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?

Usage is implied by the action 'list all', but no explicit guidance on when to use this versus siblings (e.g., mailosaur_servers_get for a single server). No when-not or alternative statements.

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