John's Essentials

generate_password

Password Generator — Generate a cryptographically secure random password with configurable length and character sets. [category: generate]

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of passwords to generate.
`length`	No	Characters per password.
`numbers`	No	Include digits 0-9. Turning all four off is the same as leaving all four on.
`symbols`	No	Include symbols from !@#$%^&*()-_=+[]{}\|;:,.<>? - quotes, backslash, backtick, tilde and slash are never used. Turning all four off is the same as leaving all four on.
`lowercase`	No	Include small letters a-z. Turning all four off is the same as leaving all four on.
`uppercase`	No	Include capital letters A-Z. Turning all four off is the same as leaving all four on.
`excludeSimilar`	No	Exclude look-alike characters (iIlL1oO0).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026
- addedInput schema / properties / length / x-ui
```
Added value: +{
+  "unit": "chars"
+}
```

Changed10 schema fields changedSep 11, 2026

changedInput schema / properties / length / description

Previous value: -"Characters per password. Values over 256 silently clamp to 256; zero or negative resets to the default 16."New value: +"Characters per password."

changedInput schema / properties / length / minimum
```
Previous value: -1New value: +4
```
changedInput schema / properties / lowercase / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / lowercase / description

Previous value: -"Include lowercase letters. NOT implied by the other flags — sending only uppercase/numbers/symbols=true yields a password with no lowercase."New value: +"Include small letters a-z. Turning all four off is the same as leaving all four on."

changedInput schema / properties / numbers / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / numbers / description

Previous value: -"Include digits 0-9. Class flags work jointly: all four false/omitted = every class enabled."New value: +"Include digits 0-9. Turning all four off is the same as leaving all four on."

changedInput schema / properties / symbols / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / symbols / description

Previous value: -"Include symbols from !@#$%^&*()-_=+[]{}|;:,.<>? — quotes, backslash, backtick, tilde and slash are never used."New value: +"Include symbols from !@#$%^&*()-_=+[]{}|;:,.<>? - quotes, backslash, backtick, tilde and slash are never used. Turning all four off is the same as leaving all four on."

changedInput schema / properties / uppercase / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / uppercase / description

Previous value: -"Include uppercase letters. If ALL four class flags (uppercase/lowercase/numbers/symbols) are omitted or false, all classes are used."New value: +"Include capital letters A-Z. Turning all four off is the same as leaving all four on."

First observedSep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description adds a meaningful behavioral claim—'cryptographically secure random'—and indicates output configurability. It does not contradict the annotations, but it omits edge-case behavior such as the all-character-sets-off fallback and excluded symbols, which are only explained in the parameter descriptions.

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?

The core behavior is conveyed in a single front-loaded sentence with no wasted explanation. The 'Password Generator —' prefix and '[category: generate]' tag are mildly redundant with the title and category, but they do not meaningfully hurt clarity.

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?

For a stateless generation tool with fully documented parameters, the description plus schema covers the essential behavior and constraints. A small gap is the absence of an explicit return-shape statement, though the output of a password generator is reasonably predictable.

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 100%, so the schema fully documents all seven parameters. The description's reference to 'length and character sets' adds no semantic value beyond what the schema already provides, earning the schema-rich baseline of 3.

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 names a specific action ('Generate') and a specific resource ('a cryptographically secure random password'), while also noting configurable length and character sets. This is unambiguous and clearly distinguishes it from the many sibling generate_* tools.

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 description provides no guidance on when to use this tool versus alternatives, nor any exclusion criteria. With siblings like generate_hash, generate_uuid, and generate_barcode nearby, the description leaves the choice entirely to inference.

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

All John's Essentials tools Inspect

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

Need Help?