Skip to main content
Glama

Passwordgen

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Generate Password

generate_password
Read-onlyIdempotent

Generate cryptographically-random password(s) (keyless, offline, CSPRNG). Control the character sets and length; returns the password(s) and their entropy in bits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoHow many to generate (1-50, default 1).
digitsNoInclude 0-9 (default true).
lengthNoPassword length (4-256, default 20).
symbolsNoInclude punctuation (default true).
lowercaseNoInclude a-z (default true).
uppercaseNoInclude A-Z (default true).
exclude_ambiguousNoExclude look-alikes (0/O, 1/l/I) (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "digits": true,
+    "length": 20,
+    "lowercase": true,
+    "symbols": true,
+    "uppercase": true
+  },
+  {
+    "count": 5,
+    "digits": true,
+    "exclude_ambiguous": true,
+    "length": 32,
+    "lowercase": true,
+    "symbols": false,
+    "uppercase": true
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: 'keyless, offline, CSPRNG' and that it returns entropy in bits. Annotations already indicate read-only, open-world, idempotent, and non-destructive.

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 sentences are highly efficient, front-loading the core purpose and key features without any redundant or irrelevant information.

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?

The description is adequate given the comprehensive schema and annotations. It mentions return values (passwords and entropy) despite no output schema. Could explicitly mention that 'count' generates multiple passwords, but the examples in the schema compensate.

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 coverage is 100%, so the schema already documents all 7 parameters. The description adds a high-level summary ('Control the character sets and length') but does not provide detailed meaning beyond what the schema offers.

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?

The description clearly states the verb ('Generate'), the resource ('cryptographically-random password(s)'), and key attributes ('keyless, offline, CSPRNG'). It distinguishes from the sibling 'generate_pin' by specifying CSPRNG and entropy return.

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 description implies usage for password generation but does not explicitly state when to use this tool vs alternatives (e.g., 'generate_pin' for numeric pins). No when-not guidance is provided.

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

All Passwordgen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources