Skip to main content
Glama
Sign In
keepassxc-mcp

keepassxc-mcp

by preginald
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_password

Create passwords using KeePassXC's configured generator settings; confirm the generated value in the generator dialog if prompted. This supplies credentials for saving or updating logins.

Instructions

Generate a password using KeePassXC's generator settings.

On some KeePassXC versions this opens the generator dialog and waits for the user to accept it.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it usefully discloses that some KeePassXC versions open a generator dialog and wait for user acceptance. However, it omits other relevant behavior such as whether the password is returned directly, what generator settings are used, or any failure conditions.

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 two short sentences with no wasted text. The core purpose is front-loaded, followed by an important behavioral caveat.

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?

The tool has no parameters and an output schema exists, so the description does not need to explain return values. It covers the core action and the notable interactive-dialog caveat, though it could say more about what the generator settings imply or what happens on versions without the dialog.

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?

There are zero input parameters, so there is no parameter semantics to document. The baseline score of 4 is appropriate because the tool takes no arguments and the description does not need to explain parameter behavior.

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 clearly states the specific action and resource: generating a password using KeePassXC's generator settings. It is unambiguous, though it does not explicitly distinguish itself from siblings like get_totp, which is a different kind of generated secret.

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 does not say when to use this tool versus alternatives, nor does it mention prerequisites. The only contextual note is about a possible dialog on some versions, which is behavioral rather than usage guidance.

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