Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_list_mailboxes

Lists available SimpleLogin mailboxes to identify valid destinations for alias forwarding and account management.

Instructions

List the mailboxes available for SimpleLogin aliases.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. "List" implies a read-only, non-destructive operation, but the description says nothing about authentication requirements, pagination, rate limits, or whether the result includes verification status. For a tool with zero annotation coverage this leaves significant behavioral questions unanswered.

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?

A single front-loaded sentence with no filler or redundant restatement of the name. It is efficient, though the extreme brevity pushes underspecification into other dimensions rather than being a structural flaw here.

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?

This is a zero-parameter read tool with no output schema, so the description should at minimum convey what a returned mailbox record looks like (e.g. email address, default flag, verification state) and any auth expectation. It conveys the object being listed but not the shape or meaning of results, leaving a modest but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to explain arguments, and the scope phrase correctly signals that no filtering input is expected.

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?

"List the mailboxes" is a specific verb plus resource, and the qualifier "available for SimpleLogin aliases" scopes it away from sl_list_aliases, which enumerates the aliases themselves. An agent can tell this is an enumeration of forwarding destinations rather than aliases. It stops short of 5 because "mailboxes" is a SimpleLogin-specific concept and the description doesn't define it or state whether verified and unverified mailboxes are both returned.

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 explicit when-to-use statement, no prerequisite (e.g. authenticated account, API key), and no routing to alternatives. The reader must infer that this is called to discover which destination addresses exist before creating or updating an alias, which is plausible but unstated. Only the phrase "available for SimpleLogin aliases" implies context, and nothing tells the agent when not to call it.

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