APIVerve

Password Generator

PasswordGenerator

Read-only

Password Generator: Password Generator creates random passwords, pronounceable strings, and multi-word passphrases configured by length, complexity, and character sets. It outputs generated strings with character counts and configuration metadata. (Cost: 1 credit)

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": "PasswordGenerator"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	The kind of password to generate. random uses the complexity preset, pronounceable builds readable syllables, passphrase joins dictionary words, and custom honours the include/exclude switches below	random
`count`	No	The number of passwords to generate
`length`	No	The length of the password to generate
`strict`	No	Guarantee at least one character from every enabled set rather than leaving it to chance
`analyze`	No	Return a strength analysis alongside each password
`mixedCase`	No	Randomly capitalise letters in a pronounceable password
`separator`	No	The character placed between passphrase words. Only applies when type is passphrase	-
`wordCount`	No	How many words a passphrase contains. Only applies when type is passphrase
`capitalize`	No	Capitalise each word of a passphrase. Only applies when type is passphrase
`complexity`	No	The complexity of the password. Only applies when type is random	medium
`excludeSimilar`	No	Exclude characters that are easy to confuse when read aloud or typed (i, l, 1, L, o, 0, O)
`includeNumbers`	No	Include digits. Applies to custom and pronounceable, and to random at simple complexity
`includeSymbols`	No	Include punctuation symbols. Applies to custom, and to random at medium complexity
`excludeAmbiguous`	No	Exclude brackets, slashes, quotes and other characters that need escaping in shells and config files
`includeLowercase`	No	Include lowercase letters in a custom password. Set false to build from the other character sets only
`includeUppercase`	No	Include uppercase letters. Applies to custom, and to random at simple complexity

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: it states the output includes character counts and configuration metadata, and discloses a 'Cost: 1 credit' charge, which is not available anywhere in the structured fields. It omits any note on the randomness/security quality of generated passwords, which is the main behavioral question for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and only two sentences, but the first sentence redundantly repeats the title twice ('Password Generator: Password Generator creates...'). The cost note is efficiently placed at the end, though the middle sentence duplicates what the output schema already declares.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 optional parameters, full schema coverage, an output schema, and clear annotations, the definition has enough to be callable without ambiguity. However, a 16-parameter generator benefits from the description explaining how the mode selection interacts with the include/exclude switches, and that guidance is left entirely to the schema.

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 all 16 parameters, including the type-mode gating rules, are documented in the schema itself. The description only echoes the mode names (random, pronounceable, passphrase) without adding any constraint, default, or interaction detail, so the baseline of 3 is appropriate.

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 uses a specific verb and resource ('creates random passwords, pronounceable strings, and multi-word passphrases') and enumerates the three main generation modes, so an agent knows exactly what the tool produces. It does not name or distinguish itself from near siblings like PasswordStrength or PasswordBreachChecker, which keeps it below 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?

There is no when-to-use guidance at all: no statement of when to call this versus PasswordStrength (to evaluate an existing password) or PasswordBreachChecker, and no exclusions or prerequisites. The purpose implies generation, but the agent must infer routing on its own.

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

All APIVerve 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.