Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_create_alias

Create a new random email alias, optionally labeled with a note for your own reference, to shield your real address when signing up for services.

Instructions

Create a new random alias. note is a label for your own use.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sl_create_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 the full behavioral burden, yet it says nothing about permissions, rate limits on random alias generation, whether the alias is immediately active, or whether generation is idempotent. Since there is also no output schema, the agent is left not knowing whether the response returns the generated alias address at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the operation front-loaded and no filler. The second sentence is a slightly clipped fragment, but nothing is wasted or 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 creation/mutation tool with zero annotation coverage, 0% schema description coverage, and no output schema, the description omits too much: the meaning of `mode`, what the tool returns, and what side effects or limits apply. An agent could call it, but not confidently.

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 description coverage is 0%, so the description must compensate, and it only explains one of two parameters: "note is a label for your own use." The `mode` parameter — likely the more consequential one, given it appears on a random-alias generator — is not mentioned anywhere and its accepted values are undocumented.

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?

The description states a specific verb and resource ("Create a new random alias"), and the qualifier "random" functionally distinguishes it from the sibling sl_create_custom_alias without naming it. It is clear what the tool produces, though it never explicitly contrasts with the custom-alias alternative.

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?

There is no guidance on when to choose this over sl_create_custom_alias or other alias tools, no prerequisites, and no exclusions. The word "random" hints at a selection criterion, but the agent must infer the whole decision rule.

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