Skip to main content
Glama

Password Generator API - strong random passwords

password_generator
Read-onlyIdempotent

Generate 1-50 random passwords with chosen length and character sets, secure random source, strength in bits. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/password-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "count": 3,
      "length": 20
    },
    "name": "password_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many, 1-50
upperNoCapital letters
digitsNoDigits
lengthNoLength 8-128
symbolsNoSymbols
clearOnlyNoLeave out look-alike characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / length / minimum
      Added value: +1
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses real operational behavior: server-side execution, immediate deletion of files with nothing stored, the entropy measure (strength in bits), and both quota and billing mechanics with the payment endpoint. One tension worth noting: the emphasis on randomness means repeated calls yield different values, which sits awkwardly with the supplied idempotentHint=true; the description is the accurate side here, so I do not treat it as a description defect, but an agent should not cache results across calls.

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

Conciseness4/5

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

Two compact sentences, front-loaded with the capability and constraints before the operational/pricing tail. Every clause carries signal (range, entropy, retention, quota, pay-per-call URL), though the 'Runs on our server' phrasing is slightly promotional where 'processed server-side, nothing retained' would be tighter.

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 stateless, fully-schema-documented generator with no output schema, the description covers what an agent needs to select and invoke it: capability, bounds, security posture, data retention, and cost/rate limits. The only gap is that it never describes the response shape (array vs. object, field names), which an agent must discover by calling.

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% and every parameter (count, length, upper, digits, symbols, clearOnly) already carries its own description and default, so the schema does the heavy lifting. The description adds only the headline bounds (1-50 passwords, chosen length/character sets) without explaining the 8-128 length range, the look-alike exclusion behavior, or default values, so 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 ('Generate ... random passwords') plus concrete scope: 1-50 count, chosen length, chosen character sets, cryptographically secure source, and strength expressed in bits. This is squarely distinguishable from the other generator siblings (qr_code_generator, hash_generator, lorem_ipsum_generator), which produce entirely different artifacts.

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?

There is no explicit when-to-use / when-not-to-use guidance and no named alternative, but usage is strongly implied by the output type (strong random passwords) and the description supplies operational context an agent needs before calling: a 25 calls/day free tier per IP and a paid x402 path at a specific URL. An agent can infer the use case but must decide on its own when this beats e.g. hash_generator.

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