Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_servers_get_password

Get the SMTP/POP3 password for a Mailosaur server to configure email clients for receiving test messages.

Instructions

Get the SMTP/POP3 password for a Mailosaur server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesServer ID.

Implementation Reference

  • src/index.ts:286-296 (registration)
    Registration of the 'mailosaur_servers_get_password' tool on the MCP server, with a zod schema requiring 'id' (string) and a handler that calls mailosaur.servers.getPassword(id).
    server.tool(
      "mailosaur_servers_get_password",
      "Get the SMTP/POP3 password for a Mailosaur server.",
      {
        id: z.string().describe("Server ID.")
      },
      async ({ id }) => {
        const result = await mailosaur.servers.getPassword(id);
        return response({ password: result });
      }
    );
  • The handler function for the tool; it calls mailosaur.servers.getPassword(id) and returns the result wrapped in a response object.
    async ({ id }) => {
      const result = await mailosaur.servers.getPassword(id);
      return response({ password: result });
    }
  • Zod schema defining the input parameter: 'id' is a required string described as 'Server ID.'
    {
      id: z.string().describe("Server ID.")
    },
  • The 'response' helper function that wraps the tool result into the MCP content response format (JSON.stringify).
    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 provided; description only states action without disclosing side effects, permissions, or how password is returned. Lacks behavioral context for an API call.

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 sentence with no extraneous words. Efficient and front-loaded.

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

Completeness4/5

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

Simple tool with one parameter and no output schema; description adequately states purpose. Could mention typical usage or error cases, but sufficient for basic understanding.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter 'id', so baseline is 3. Description does not add additional meaning beyond the schema.

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?

Clear verb 'Get' and specific resource 'SMTP/POP3 password' for a Mailosaur server, distinct from sibling tools like mailosaur_servers_get.

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 vs alternatives such as mailosaur_servers_get or when password is needed. Implies usage only through name and description.

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