Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Generate Username

keychain_generate_username
Read-only

Generate usernames via random word, plus-addressed email, catch-all, or forwarded alias. Never mutates the vault; reveal=true returns the value, otherwise redacted.

Instructions

Generate a username like the Bitwarden generator (random word, plus-addressed email, catch-all, forwarded alias). This never mutates the vault; pass reveal=true to return the value, and NOREVEAL or KEYCHAIN_NOREVEAL force redaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoUsername generation strategy: random word, plus-addressed email, catch-all email, or forwarded alias.
emailNoBase email address for plus-addressed username generation.
domainNoDomain for catch-all email username generation.
revealNoWhether secret values are returned; default false and can be forced false by NOREVEAL.
capitalizeNoCapitalize the generated random word when supported.
includeNumberNoAppend a number to generated usernames when supported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.35
    • removedOutput schema / properties / result / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / result / properties / value / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed7 schema fields changedv0.2.19
    • addedInput schema / properties / capitalize / description
      Added value: +"Capitalize the generated random word when supported."
    • addedInput schema / properties / domain / description
      Added value: +"Domain for catch-all email username generation."
    • addedInput schema / properties / email / description
      Added value: +"Base email address for plus-addressed username generation."
    • addedInput schema / properties / includeNumber / description
      Added value: +"Append a number to generated usernames when supported."
    • addedInput schema / properties / reveal / description
      Added value: +"Whether secret values are returned; default false and can be forced false by NOREVEAL."
    • addedInput schema / properties / type / description
      Added value: +"Username generation strategy: random word, plus-addressed email, catch-all email, or forwarded alias."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "const": "generated",
+          "type": "string"
+        },
+        "revealed": {
+          "type": "boolean"
+        },
+        "value": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "kind",
+        "value",
+        "revealed"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  3. Addedv0.1.20

TDQS

A4/5.0
Behavior4/5

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

The description explicitly states that the tool never mutates the vault, which is valuable behavioral context consistent with the readOnlyHint annotation. It also discloses reveal behavior and redaction enforcement via NOREVEAL/KEYCHAIN_NOREVEAL, adding detail beyond the annotation alone.

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 description is two sentences with no filler. It front-loads the core action and strategy list, then adds the critical safety and redaction behavior without unnecessary detail.

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?

The description, combined with the full input schema, readOnlyHint annotation, and output schema, provides sufficient context for an agent to call this tool correctly. It covers the generation strategies, safety guarantees, and reveal/redaction mechanics; no critical behavior is left unexplained.

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?

Since schema description coverage is 100%, the schema already documents each parameter. The description adds meaningful context around the reveal parameter by explaining that NOREVEAL or KEYCHAIN_NOREVEAL forces redaction, and frames the type parameter through the Bitwarden generator analogy, which helps an agent select appropriate strategies.

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 clearly identifies the tool as a username generator with specific strategies (random word, plus-addressed email, catch-all, forwarded alias). It does not explicitly differentiate itself from siblings like keychain_generate or keychain_get_username, though the specific 'username' focus makes the purpose reasonably distinct.

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 verb 'generate' and the strategy list imply when this tool should be used, but the description provides no explicit guidance on when to choose this tool over alternatives such as keychain_get_username or keychain_generate. It also does not state when specific parameter combinations are needed, leaving usage largely to inference.

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