GadgetHumans API Hub

by io.github.scotia1973-bot

generate_password

Generate secure random passwords

Input Schema

Name	Required	Description
`count`	No	Number of passwords (default: 1)
`length`	No	Password length (default: 16)
`numbers`	No
`symbols`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 10, 2026

removedInput schema / properties / count / default
```
Removed value: -1
```
addedInput schema / properties / count / description
```
Added value: +"Number of passwords (default: 1)"
```
removedInput schema / properties / count / title
```
Removed value: -"Count"
```
removedInput schema / properties / length / default
```
Removed value: -16
```
addedInput schema / properties / length / description
```
Added value: +"Password length (default: 16)"
```
removedInput schema / properties / length / title
```
Removed value: -"Length"
```

removedInput schema / properties / lowercase

Removed value: -{
-  "default": true,
-  "title": "Lowercase",
-  "type": "boolean"
-}

removedInput schema / properties / numbers / default
```
Removed value: -true
```
removedInput schema / properties / numbers / title
```
Removed value: -"Numbers"
```
removedInput schema / properties / symbols / default
```
Removed value: -true
```
removedInput schema / properties / symbols / title
```
Removed value: -"Symbols"
```

removedInput schema / properties / uppercase

Removed value: -{
-  "default": true,
-  "title": "Uppercase",
-  "type": "boolean"
-}

removedInput schema / title

Removed value: -"generate_passwordArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "generate_passwordOutput",
-  "type": "object"
-}New value: +null

First observedJul 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Secure random' hints at a cryptographic source but does not disclose entropy guarantees, output format, or whether generated values are stored or returned. For a security-sensitive generator with zero annotation coverage, this is thin.

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?

A single short, front-loaded sentence with no filler. It is efficient, though arguably too terse given the tool's configuration surface.

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?

Four parameters, no annotations, no output schema, and half the parameters undocumented. The description should at least sketch the output (list vs. single string) and defaults, but leaves the agent to infer everything from the schema alone.

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 coverage is only 50% – 'numbers' and 'symbols' booleans have no descriptions anywhere. The description adds nothing about count, length, or what those booleans default to, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Generate) and resource (secure random passwords) that an agent can act on immediately. It does not, however, distinguish itself from the sibling check_password_strength or clarify scope (bulk generation, character sets).

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 when-to-use context, no exclusions, and no mention of the adjacent check_password_strength tool that an agent might reasonably confuse this with. The agent gets no help deciding whether this is the right tool.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?