Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

mailosaur_servers_generate_email_address

Generate a random email address for a Mailosaur server to use in email testing workflows.

Instructions

Generate a random email address for a Mailosaur server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesServer ID.

Implementation Reference

  • src/index.ts:325-335 (handler)
    The handler for the 'mailosaur_servers_generate_email_address' tool. It takes a server 'id', calls mailosaur.servers.generateEmailAddress(id) to generate a random email address, and returns it as JSON.
    server.tool(
  "mailosaur_servers_generate_email_address",
  "Generate a random email address for a Mailosaur server.",
  {
    id: z.string().describe("Server ID.")
  },
  async ({ id }) => {
    const emailAddress = mailosaur.servers.generateEmailAddress(id);
    return response({ emailAddress });
  }
);
  • src/index.ts:328-329 (schema)
    Input schema for the tool: requires 'id' (string) as the server ID.
    {
  id: z.string().describe("Server ID.")
  • src/index.ts:325-325 (registration)
    The tool is registered via server.tool() call with the name 'mailosaur_servers_generate_email_address'.
    server.tool(

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states that an email address is generated, but omits important details such as whether the address is persistent, if it supports email reception, or any side effects. The description is minimal and lacks transparency.

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 description is a single, concise sentence that conveys the tool's purpose without any superfluous words. It is front-loaded and efficiently communicates the core functionality.

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?

Given the tool's simplicity (one parameter, no output schema), the description is incomplete. It does not explain what the generated email address can be used for, its lifetime, or any related operations. Basic contextual information is missing.

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 100% but the parameter description 'Server ID' provides no additional meaning beyond the schema. The tool description does not elaborate on the parameter's role or constraints (e.g., format, source of the ID). It adds no value 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?

The description clearly states the action ('Generate a random email address') and the resource ('for a Mailosaur server'). It is specific and unambiguous, using a verb+resource structure that directly 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 Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., when creating a test email address vs. listing servers). An agent would have no guidance on context or prerequisites.

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