Skip to main content
Glama
wundervault

wundervault

Official

vault_2fa_code

Retrieve the current 6- or 8-digit authenticator code and its remaining validity from a vaulted 2FA secret, so you can complete a sign-in that prompts for one. The seed stays in the broker.

Instructions

Get the current authenticator-app code (the 6-digit 2FA code) for a vaulted login or Authenticator code secret, to type into a sign-in that asks for one. You get the 6- or 8-digit code and how many seconds it stays valid; the seed that makes the codes never leaves the broker. If the code was about to expire, this waits up to 5 seconds and returns the next one.

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": {
      "entry_id": "<entry_id>",
      "purpose": "<purpose>"
    },
    "name": "vault_2fa_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeYesWhat you are signing in to, and why. The owner sees it.
entry_idYesVault entry holding the authenticator setup key (an Authenticator code secret, or a login with its Authenticator setup key filled). Only authenticator-app codes: not text-message or email codes, not passkeys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses the return shape (6- or 8-digit code plus remaining validity seconds), a security property (the seed never leaves the broker), and a non-obvious timing behavior (waits up to 5 seconds and returns the next code if about to expire). It stops short of saying whether the call is logged/visible or what errors occur for a non-authenticator entry.

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?

Three tight sentences: what it returns first, then the security assurance, then the edge-case timing behavior. Nothing is redundant and the most operationally important fact is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description supplies both the returned value semantics and the security/timing behavior an agent needs to call it correctly and interpret the result.

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 coverage is 100%, so both parameters are already documented, including the exclusions for SMS/email codes and passkeys. The description adds no meaning about entry_id or purpose beyond what the schema states, so the baseline 3 applies.

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?

The description gives a specific verb and resource ('Get the current authenticator-app code... for a vaulted login or Authenticator code secret') and names exactly what is returned. It is unmistakable against siblings like vault_git, vault_pay, or vault_sign, none of which produce OTP codes.

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?

It states the context of use clearly: 'to type into a sign-in that asks for one,' which tells the agent the trigger condition. It does not name an alternative tool or explicitly state when not to use it, though no plausible sibling alternative exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.