Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_create_custom_alias

Creates a custom email alias with a chosen prefix using a signed suffix and mailbox IDs retrieved from alias options, routing mail to selected mailboxes.

Instructions

Create a custom alias with a chosen prefix. Get signed_suffix and mailbox_ids from sl_alias_options first.

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": {
      "alias_prefix": "<alias_prefix>",
      "signed_suffix": "<signed_suffix>",
      "mailbox_ids": "<mailbox_ids>"
    },
    "name": "sl_create_custom_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
noteNo
hostnameNo
mailbox_idsYes
alias_prefixYes
signed_suffixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a creation/mutation tool. Beyond the word "Create", it says nothing about whether the alias goes live immediately, whether the prefix must be unique, what permissions are needed, or what happens on conflict. The one behavioral fact it does disclose — the dependency on sl_alias_options — is useful but limited.

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?

Two short sentences with no filler, and the essential prerequisite is front-loaded right next to the action statement. Nothing needs trimming and nothing is buried.

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 6-parameter write tool with no annotations, no output schema, and zero schema-level parameter documentation, the description is too thin. It omits the three optional parameters entirely and gives no picture of the result or side effects, so an agent still has to guess at much of the call.

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 0% across 6 parameters, so the description must compensate, and it partially does: it explains the provenance of the two non-obvious required values, signed_suffix and mailbox_ids. The optional name, note, and hostname parameters are left completely undefined, and no format or constraint is given for alias_prefix beyond "chosen".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a custom alias with a chosen prefix" gives a specific verb and resource and, via "custom" and "chosen prefix", signals how it differs from the plain sibling sl_create_alias. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives a concrete prerequisite and names the sibling that supplies it: signed_suffix and mailbox_ids must come from sl_alias_options first. That is real when-to-use guidance, but there is no statement about when to prefer sl_create_alias instead or what preconditions validate the prefix.

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