Skip to main content
Glama

gen_password

Paid $0.02 (x402, USDC Base): CSPRNG password/API-secret generator, 8-128 chars, classes upper/lower/digits/symbols, entropy estimate. Args: length (int, default 20).

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

Input Schema

NameRequiredDescriptionDefault
lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose two valuable facts: a $0.02 x402/USDC-Base payment requirement and that output includes an entropy estimate. It omits other behavior an agent needs, notably what happens on payment failure, whether the charge is per call, and whether the returned secret is single-use or repeatable. The listed classes (upper/lower/digits/symbols) also imply configurability that the schema does not expose.

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?

One sentence, front-loaded with the payment caveat and then the core capability, followed by a compact argument note with no filler. It is dense to the point of feeling crammed, but no clause is wasted.

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 one-parameter, no-output-schema tool, the description covers cost, algorithm quality, length bounds and the entropy-estimate return value – enough to call it correctly. The gap is the mismatch between the four advertised character classes and a schema that only accepts length, which could mislead an agent into expecting a classes argument.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate for the single undocumented parameter – and it does, supplying type, the default value of 20 (absent from the schema), and the 8-128 working range. It does not clarify whether the stated character classes are fixed behavior or a hidden option.

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?

The description gives a specific verb + resource: a 'CSPRNG password/API-secret generator', which separates it in kind from siblings like gen_uuid, gen_random and gen_lorem. It never names or routes against those siblings explicitly, so the differentiation is inferential rather than stated.

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 by the noun phrase 'password/API-secret' – an agent can infer this is the credentials tool rather than the random-string or UUID tool. There is no explicit when-to-use, when-not-to-use, or 'prefer X over gen_random for secrets' guidance.

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