Skip to main content
Glama

generate_password

Generate secure random passwords for account creation, temporary credentials, or API keys. Customize length, character types, and number of passwords.

Instructions

Generate one or more secure random passwords.

Use this when a user needs a strong, random password — for account creation,
temporary credentials, API keys, or any security-sensitive use case.

Parameters:
    length    — Length of each password (4-256, default: 16).
    count     — Number of passwords to generate (1-50, default: 1).
    numbers   — Include digits 0-9 (default: True).
    symbols   — Include special characters like !@#$%^&* (default: True).
    uppercase — Include A-Z (default: True).
    lowercase — Include a-z (default: True).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lengthNo
countNo
numbersNo
symbolsNo
uppercaseNo
lowercaseNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description carries full burden. It notes 'secure random passwords' but lacks details about the random source, performance, or edge cases. Adequate for a simple generator but not rich.

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 concise with a front-loaded purpose sentence followed by clear parameter definitions. No wasted words, every sentence adds value.

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?

Given the presence of an output schema, return values are covered. The description fully explains input parameters and the tool's function, making it complete for a password generator.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description explicitly lists all 6 parameters with ranges, defaults, and what values control (e.g., 'numbers — Include digits 0-9'), adding essential meaning beyond the schema.

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 'Generate one or more secure random passwords' and distinguishes this tool from sibling generators (e.g., generate_random_numbers, generate_uuid) by specifying the use case for passwords.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this when a user needs a strong, random password — for account creation...', providing clear context. However, it does not mention when not to use or alternative tools for non-password random generation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server