Skip to main content
Glama
Sign In
keepassxc-mcp

keepassxc-mcp

by preginald
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_database_groups

Lists the group and folder tree of an unlocked KeePassXC database so you can locate and manage password entries by group without opening the .kdbx file.

Instructions

List the group/folder tree of the unlocked database.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the implicit state dependency (database must be unlocked) which is real added context. It does not say what happens if the database is locked (error vs empty) or note that this is a non-mutating read, though the verb 'List' implies read-only.

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?

A single front-loaded sentence with no filler; every word (list, group/folder tree, unlocked) contributes to correct invocation.

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?

With an output schema present and zero parameters, the description need not explain return values, and the 'unlocked' qualifier covers the main precondition. The only meaningful gap is the failure mode when the database is locked.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The only semantic element, the required database state, is covered by the 'unlocked' qualifier.

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 (list) and resource (group/folder tree) scoped to the unlocked database, which is enough for an agent to know exactly what it retrieves. It stops short of naming a sibling such as get_logins or create_group to differentiate the read-tree view from them.

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 phrase 'of the unlocked database' implies the prerequisite that unlock_database must run first, which is useful, but it is left implicit rather than stated. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings.

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