Skip to main content
Glama

Get Password

keychain_get_password
Read-only

Retrieve stored login passwords from your Bitwarden vault using search terms. Enable reveal mode to access password values securely through the Warden MCP Server.

Instructions

Get a login password by search term (bw get password). Returning a password requires reveal=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
revealNo

Implementation Reference

  • The tool definition and handler implementation for `keychain_get_password` (aliased in the code as `${deps.toolPrefix}.get_password`).
      `${deps.toolPrefix}.get_password`,
      {
        title: 'Get Password',
        description:
          'Get a login password by search term (bw get password). Returning a password requires reveal=true.',
        annotations: { readOnlyHint: true },
        inputSchema: {
          term: z.string(),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const password = await sdk.getPassword(
          { term: input.term },
          { reveal: effectiveReveal(input) },
        );
        return {
          structuredContent: toolResult(
            'password',
            password.value,
            password.revealed,
          ),
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds useful context about the reveal parameter requirement for password retrieval, which isn't covered by annotations. However, it lacks details on authentication needs, rate limits, or what happens if multiple matches exist for the search term.

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 concise sentences with zero waste. The first sentence states the purpose, and the second provides critical usage information about the reveal parameter. Every word earns its place, and the structure is front-loaded with essential information.

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?

Given no output schema and 0% schema description coverage, the description compensates somewhat by explaining parameter semantics. However, for a tool that retrieves sensitive data (passwords), it lacks details on authentication requirements, error conditions, or return format. The annotations cover safety but not operational context.

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 0%, so the schema provides no parameter documentation. The description clarifies that 'term' is a search term and 'reveal' is required to return a password, adding meaningful semantics beyond the bare schema. However, it doesn't explain the format of 'term' or the implications of reveal=false.

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 action ('Get a login password') and resource ('by search term'), with the parenthetical '(bw get password)' reinforcing the specific operation. It distinguishes from siblings like 'keychain_get_username' or 'keychain_get_item' by focusing on passwords, but doesn't explicitly contrast with similar tools like 'keychain_search_items'.

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 description implies usage by stating 'Returning a password requires reveal=true', which suggests when to use the reveal parameter. However, it provides no explicit guidance on when to choose this tool over alternatives like 'keychain_get_item' or 'keychain_search_items', nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icoretech/warden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server