Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_alias_options

Retrieves signed suffixes and mailboxes for creating a custom alias; optionally pass a hostname to get a site-specific suffix.

Instructions

Get the signed suffixes and mailboxes available for creating a custom alias. Pass hostname (e.g. 'example.com') for a site-specific suffix.

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

Input Schema

NameRequiredDescriptionDefault
hostnameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral load; it implies a read-only lookup and discloses what the response contains (signed suffixes plus mailboxes) and how hostname changes the result. It says nothing about permissions, whether results are scoped to the authenticated account, or how the mailbox list is filtered.

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 zero filler; what the tool returns comes first and the one parameter's effect follows immediately. Nothing is repeated from structured fields unnecessarily.

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 one-parameter, read-only discovery tool with no output schema, the description covers purpose, return contents, and the parameter's effect. The only real gap is the relationship to sl_list_mailboxes, whose results may overlap.

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?

Schema coverage is 0% and the single hostname parameter is undocumented in the schema, so the description does real work here: it gives the expected format ('example.com') and explains the behavioral effect, that a hostname yields a site-specific suffix rather than the default set.

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 uses a specific verb ('Get') and names the exact resources returned: signed suffixes and mailboxes for creating a custom alias. That is enough to tell it apart from mutation siblings like sl_create_custom_alias, but it does not address overlap with sl_list_mailboxes, which also surfaces mailboxes.

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 by the phrase 'available for creating a custom alias', which suggests calling this before sl_create_custom_alias. There is no explicit when-to-use statement, no exclusion, and no pointer to sl_list_mailboxes as an alternative for mailbox listing.

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