Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_delete_alias

Deletes a SimpleLogin alias by ID, permanently removing it and preventing further use. Use this when an alias is no longer needed and irreversible deletion is intended.

Instructions

Delete a SimpleLogin alias by ID. This cannot be undone.

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_id": "<alias_id>"
    },
    "name": "sl_delete_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
alias_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly discloses irreversibility, which is the single most important behavior for a destructive operation, but it omits auth requirements, what happens to mail already forwarded through the alias, and whether the alias address can be reused.

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 the action front-loaded and the destructive warning attached immediately after. Nothing here is wasted or padded.

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?

For a single-parameter destructive tool with no output schema and no annotations, the core facts an agent needs before calling are present: what is deleted, how it is identified, and that the effect is permanent. Only secondary details, such as permission needs and side effects on forwarding, are missing.

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%, so the description must compensate. It states the identifier is an alias 'ID', which is the minimum needed to avoid passing an email address or an alias note, but it gives no format detail (numeric vs string) beyond what the schema's integer type already implies.

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 names a concrete verb and resource: 'Delete a SimpleLogin alias by ID.' An agent can tell this apart from sl_create_alias, sl_update_alias, and sl_toggle_alias just from the verb, even though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

'This cannot be undone' implies caution and suggests the agent should treat deletion as a last resort, but it never states when deletion is preferred over alternatives like sl_toggle_alias (which disables rather than destroys). No prerequisites or preconditions are given.

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