Underground Cultural District MCP Server

generate-password

Generate secure random passwords from 8 to 128 characters. Customize length, numbers, symbols, and case for strong passwords.

Instructions

Generate a secure random password (8–128 chars).

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

Name	Required	Description
`length`	No	Length (default 16)
`includeNumbers`	No
`includeSymbols`	No
`includeUppercase`	No
`includeLowercase`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.1.0Apr 17, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided; description only mentions 'secure random password' but does not specify cryptographic details, output format, or any side effects. Minimal disclosure beyond the basic action.

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?

Single sentence with no redundant information. Efficiently conveys purpose and length constraint.

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?

For a simple password generator with no output schema, the description does not explicitly state that the output is a string. However, the action implies it. Lacks mention of default behavior for boolean parameters.

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

Parameters2/5

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

Schema description coverage is only 20% (only length has a description). The tool description does not add any parameter semantics beyond the schema; booleans like includeNumbers are left implicit.

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?

Clear verb and resource: 'Generate a secure random password', with specific length range (8–128 chars). Distinct from siblings like generate-uuid.

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?

No guidance on when to use this tool versus alternatives like generate-uuid or generate-hash. No context about preferred use cases.

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