Skip to main content
Glama
Sign In
publicsofttools-mcp

publicsofttools-mcp

by DrEjazAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

generate_password

Generate cryptographically secure passwords with customizable length, uppercase, numbers, and symbols.

Instructions

Generate a cryptographically secure random password with configurable rules.

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
lengthNoPassword length (default: 16, max: 128)
uppercaseNoInclude uppercase letters (default: true)
numbersNoInclude numbers (default: true)
symbolsNoInclude symbols (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'cryptographically secure' and 'random', but does not address potential side effects, authorization requirements, or data privacy (e.g., whether passwords are stored or logged).

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place, with no fluff or repetition.

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

Completeness2/5

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

Given that there is no output schema and no annotations, the description should explain the return value (e.g., the generated password string). It also lacks details on character set composition or limitations, making it incomplete for a four-parameter tool.

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?

The input schema has 100% description coverage, meaning all four parameters are already documented with defaults. The description adds 'configurable rules' but does not provide new semantic meaning beyond what the schema offers. Baseline 3 is appropriate.

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 the tool generates a cryptographically secure random password with configurable rules. It uses a specific verb ('generate') and resource ('password'), and the security and configurability details distinguish it from sibling tools like generate_hash or 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or comparisons to sibling tools such as generate_uuid, which also generates random strings.

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

Deploy Server

Other Tools