Mailosaur MCP

mailosaur_devices_create

Create a virtual security device by providing a base32 shared secret, enabling TOTP-based authentication in Mailosaur testing environments.

Instructions

Create a Mailosaur virtual security device from a base32 shared secret.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sharedSecret": "<sharedSecret>"
    },
    "name": "mailosaur_devices_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`sharedSecret`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 18, 2026

TDQS

B3.1/5.0

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 only mentions creation from a shared secret, omitting details such as idempotency, required permissions, error states, or return behavior.

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?

A single, front-loaded sentence with no wasted words. Every part 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?

With no output schema or annotations, the description lacks details on return values, device purpose, or parameter nuances. For a simple create, it is barely adequate.

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 0%, so description should compensate. It adds value by noting the sharedSecret is base32, but does not explain the optional 'name' parameter or any constraints.

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 uses a specific verb 'Create' and resource 'Mailosaur virtual security device', and specifies the input 'base32 shared secret', clearly distinguishing it from sibling tools like delete, list, 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, nor any prerequisites or exclusions. The description simply states what it does without context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server