Skip to main content
Glama
Sign In
keepassxc-mcp

keepassxc-mcp

by preginald
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_totp

Retrieve the current TOTP code for a KeePassXC entry by UUID, using the UUID returned from get_logins, so MCP clients can complete two-factor authentication.

Instructions

Get the current TOTP code for an entry UUID (from get_logins).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuid": "<uuid>"
    },
    "name": "get_totp"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 disclosure burden. It implies a time-sensitive, ephemeral secret ('current') but says nothing about whether the database must be unlocked first (relevant given unlock/lock_database siblings), whether the code is single-use, or how errors surface for entries lacking TOTP.

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 sentence with no filler, front-loaded with the action and result, with the sourcing hint in parentheses. Every clause earns its place.

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?

An output schema exists, so return values need no explanation. However, for a secret-retrieval tool with zero annotations, the description omits the unlock prerequisite and error cases, leaving meaningful operational gaps.

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 coverage is 0% and the uuid property has no description, so the description must compensate. It does so by specifying that the UUID identifies a login entry and must come from get_logins, which is exactly the semantic the schema lacks. It stops short of format details (UUID vs. entry ID variants).

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

Purpose5/5

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

Specific verb ('Get') plus specific resource ('current TOTP code') and the identifier type it operates on. It clearly separates itself from siblings like generate_password (password generation) and get_logins (credential listing) without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'(from get_logins)' establishes the prerequisite workflow: obtain the entry UUID via get_logins first. It gives clear context for invocation but names no exclusions or failure alternatives (e.g., what to do for entries without a TOTP secret).

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