Skip to main content
Glama
enthouan

simplelogin-mcp

by enthouan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update account settings

settings_update
Idempotent

Update account-wide alias settings by changing only the fields you provide; returns the resulting configuration. Manage notification, sender format, alias generator, suffix, and default domain.

Instructions

Update the account-wide alias settings; only the provided fields change and the resulting settings are returned. Deliberately limited to the five documented alias-behavior fields: account email, password, payment, and deletion are out of scope and stay in the web UI. random_alias_default_domain must be a domain from alias_domains_list (premium-only domains need a premium account; a custom domain must be yours and verified). A call that changes nothing is rejected without contacting SimpleLogin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notificationNoWhether SimpleLogin sends the user email notifications.
sender_formatNoHow the original sender appears in forwarded mail. For john@wick.com ("John Wick"): AT = "John Wick - john at wick.com", A = "John Wick - john(a)wick.com", NAME_ONLY = "John Wick", AT_ONLY = "john at wick.com", NO_NAME = no sender shown.
alias_generatorNoAddress style for random aliases: "word" (word-based) or "uuid".
random_alias_suffixNoSuffix style for random and on-the-fly aliases: "word" (dictionary word) or "random_string".
random_alias_default_domainNoDomain used for random aliases; one of the domains from alias_domains_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-update semantics ("only the provided fields change"), that resulting settings are returned, that no-op calls are rejected before contacting the server, and the validation rules for random_alias_default_domain (premium/verified requirements). These are non-obvious operational behaviors an agent needs before calling.

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 scope constraint and update semantics are front-loaded in the first sentence, and each subsequent sentence delivers distinct information (validation rules, rejection behavior) with no filler.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers the important gaps: partial-update behavior, the returned result, validation preconditions, and what is explicitly out of scope. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine cross-field semantics the schema lacks: the domain parameter must come from alias_domains_list, premium domains require a premium account, and custom domains must be owned and verified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update the account-wide alias settings") and immediately bounds the scope to the five documented alias-behavior fields. An agent can distinguish this from settings_get and alias_update without opening either schema.

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

Usage Guidelines4/5

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

Clearly frames when to use it (alias-behavior fields only) and when not to (account email, password, payment, deletion stay in the web UI), which is unusually explicit exclusion guidance. It stops short of naming a sibling tool for those other settings, so it is clear context rather than a full routing rule.

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

Deploy Server

Other Tools