Skip to main content
Glama
simplelogin-mcp

simplelogin-mcp

by codepilots

sl_whoami

Checks the configured SimpleLogin API key and returns the account email, so you can verify credentials before managing aliases.

Instructions

Check the configured API key and return the SimpleLogin account email.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. "Check" plus zero parameters implies a read-only probe, but the description never says what happens on an invalid or expired key (error vs. empty result) or whether the call has any side effects or rate limits.

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?

A single front-loaded sentence with zero padding. The action and the return value are both packed into eleven words with no redundancy.

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?

With no output schema, the description must say what comes back, and it does (the account email), which covers the main need for a trivial zero-param tool. The remaining gap is failure semantics, which matters here because the tool's whole purpose is validating a credential.

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 input schema has no properties at all, so there is nothing for the description to disambiguate; baseline is 4. It correctly implies the tool takes no caller-supplied arguments by describing the key as "configured" rather than passed in.

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?

"Check the configured API key and return the SimpleLogin account email" pairs a specific verb (check/return) with a specific resource (API key, account email). It is immediately distinguishable from the alias-management siblings, which all operate on alias objects rather than credential identity.

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?

The use case (verify the key works, discover which account is configured) is implied by the wording but never stated as a when-to-use rule, and no alternatives or exclusions are named. For a zero-parameter identity probe the implication is reasonably safe, so this is adequate rather than strong.

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