Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_get_alias

Retrieve a SimpleLogin email alias using its numeric ID to view alias details for management or reference.

Instructions

Get one SimpleLogin alias by numeric ID.

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_get_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
alias_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, yet it discloses almost nothing beyond "read." It does not say whether a missing or deleted ID errors out, what auth/account scope applies, or whether the response includes alias details like note or mailbox.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Nothing in it needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It is a simple single-parameter read tool with no output schema, so the bar is low, but the description still leaves the return contents and failure behavior undefined. For a lookup tool where an agent must know what it gets back, this is adequate but incomplete.

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 coverage is 0% and the single parameter is documented only as a bare integer titled "Alias Id." The description rescues this by specifying the ID is numeric and identifies an alias specifically, but adds no format, range, or source-of-ID guidance.

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?

States a specific verb and resource ("Get one SimpleLogin alias") and constrains the lookup key to a numeric ID, which separates it from list-style siblings like sl_list_aliases. It does not name the sibling it complements, so an agent must infer the routing itself.

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?

Usage is only implied: the phrase "by numeric ID" suggests it applies when an ID is already known and a single record is wanted. There is no explicit when-not guidance (e.g., what to do if you only have an email address), and no alternative is named.

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