Skip to main content
Glama

Generate password

generate_password
Read-only

Generates a random secure password of the requested length and character sets. Passwords are generated with cryptographic randomness and are never stored or sent anywhere.

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

Input Schema

NameRequiredDescriptionDefault
digitsNoInclude digits (0-9).
lengthNoPassword length (4-128).
symbolsNoInclude symbols (!@#$%^&* etc.).
lowercaseNoInclude lowercase letters (a-z).
uppercaseNoInclude uppercase letters (A-Z).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them with genuinely useful security context: cryptographic randomness and the guarantee that passwords are never stored or sent anywhere, which matters for a credential-generating tool.

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 tight sentences, zero filler, with the core action front-loaded and the security guarantees appended as supporting context. Nothing is repeated from the title or schema verbatim.

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 five-parameter, zero-required utility with full schema coverage and annotations, the description covers purpose, randomness source, and data-handling guarantees. The only minor gap is that the return shape (a plain password string) is left implicit, though with no output schema and such a simple tool that is a small omission.

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%, including defaults and the 4-128 range, so the schema already carries parameter meaning. The description only restates that length and character sets are configurable, adding no syntax or constraint detail beyond it — baseline 3 applies.

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?

States a specific verb and resource ("Generates a random secure password") plus the two controlling dimensions (length and character sets). No sibling in the provided list produces passwords, so there is no ambiguity to resolve.

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?

Usage is only implied: the name and description make it obvious you call this when you need a password, and the sibling tools are unrelated utilities with no overlap. There is no explicit when-to-use or when-not-to-use statement, but none is really needed for a self-contained utility.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources