Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_list_aliases

Lists email aliases newest first, with an optional search query and page selection. Use it to browse or find existing aliases in your SimpleLogin account.

Instructions

List aliases (newest first), optionally filtered by a search query.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that results are ordered newest first and that filtering is optional, but it says nothing about pagination behavior, result limits, permissions, or what the page_id parameter does.

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?

The description is a single efficient sentence with no wasted wording, and the ordering detail is front-loaded alongside the core listing behavior.

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 list tool with two parameters, no annotations, and no output schema, the description is under-specified. The unexplained page_id parameter and missing pagination behavior are significant gaps for correct invocation.

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. It clarifies that 'query' is an optional search filter, but it completely omits any explanation of the page_id parameter, leaving pagination semantics undocumented in both the schema and the description.

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: 'List aliases', and adds the useful ordering detail 'newest first'. It implicitly distinguishes listing from single-alias operations like sl_get_alias, though it does not explicitly name a sibling 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?

The phrase 'optionally filtered by a search query' gives minimal usage context, but there is no explicit guidance on when to use this tool versus alternatives such as sl_get_alias or sl_list_mailboxes. No exclusions or prerequisites are stated.

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