Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_update_alias

Update an existing SimpleLogin alias's name or note to keep alias details accurate and organized.

Instructions

Update the note and/or name of an existing SimpleLogin alias.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
noteNo
alias_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It hints at partial-update semantics via 'and/or' but never states whether null clears a field, whether omitted fields are left untouched, what permissions are needed, or whether the change is reversible.

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; the mutable fields are stated immediately after the verb. It is appropriately sized for what it says, though brevity here reflects under-specification rather than economy.

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 mutation tool with no annotations, no output schema, and zero parameter descriptions in the schema, this one-sentence description is too thin. An agent cannot tell what the response looks like, what happens on partial input, or how failures are signaled.

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 description coverage is 0%, so the description must compensate. It names two of the three parameters (name, note) and the 'and/or' phrasing implies both are optional, but alias_id is never explained and no value formats or null-clearing semantics are given.

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?

Names a specific verb (Update) and the exact mutable fields (note and/or name) on a named resource (SimpleLogin alias), which is enough to distinguish it from sl_get_alias, sl_toggle_alias, and sl_delete_alias. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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 word 'existing' implies an alias must already exist, but there is no explicit when-to-use guidance, no mention of when to prefer this over sl_toggle_alias or sl_delete_alias, and no prerequisites stated. An agent must infer the use case entirely.

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