Skip to main content
Glama

dev_tools_password_generate

[$x402 pago por llamada] Genera contraseñas aleatorias usando el RNG del sistema operativo.

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

Input Schema

NameRequiredDescriptionDefault
countNoCuántas contraseñas generar (1-20). Default: 1.
lengthNoLongitud de cada contraseña (8-128). Default: 16.
numbersNoIncluir números. Default: true.
symbolsNoIncluir símbolos. Default: true.
uppercaseNoIncluir mayúsculas. Default: true.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does add real behavioral context: it discloses the payment model (paid per call) and the underlying randomness source (OS RNG), both of which matter for trust and cost decisions. It stops short of stating that the operation is side-effect free or describing what is returned, which keeps it from a 5.

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 efficient sentence with the cost marker bracketed up front so the agent sees the payment implication before the purpose. No wasted words, though the bracket prefix slightly buries the core purpose.

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 six-parameter generator with no output schema, the description explains the mechanism and cost model but never says what the result looks like (e.g. a list of plaintext passwords when count > 1) or how the 402 flow resolves. Taskable, but an agent still has to infer the return shape.

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%, so all six parameters (count, length, numbers, symbols, uppercase, x_payment) are fully documented in the schema with defaults and ranges. The description adds nothing about parameters beyond what the schema already states, so the baseline 3 is correct.

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 names a specific verb and resource ('Genera contraseñas aleatorias') plus the entropy source ('RNG del sistema operativo'), which tells an agent this is CSPRNG-backed rather than a toy generator. It does not explicitly distinguish itself from nearby siblings such as dev_tools_uuid_generate or dev_tools_totp, so it falls short of a 5.

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?

The '$x402 pago por llamada' prefix signals this is a metered/paid operation, which implicitly guides an agent to use it deliberately rather than in bulk loops. However, there is no explicit when-to-use versus when-not guidance and no reference to alternative siblings for related secret-generation needs.

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