Skip to main content
Glama

Get Password History

keychain_get_password_history
Read-only

Retrieve password history for a vault item to track changes over time. Use reveal parameter to view actual passwords when needed.

Instructions

Get an item password history (if any). Returning passwords requires reveal=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
revealNo

Implementation Reference

  • Registration of the "keychain_get_password_history" tool and its handler function.
      `${deps.toolPrefix}.get_password_history`,
      {
        title: 'Get Password History',
        description:
          'Get an item password history (if any). Returning passwords requires reveal=true.',
        annotations: { readOnlyHint: true },
        inputSchema: {
          id: z.string(),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const history = await sdk.getPasswordHistory(input.id, {
          reveal: effectiveReveal(input),
        });
        return {
          structuredContent: toolResult(
            'password_history',
            history.value,
            history.revealed,
          ),
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior4/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds valuable context beyond this: it discloses that passwords may not be returned by default (requiring reveal=true) and hints at conditional data availability ('if any'), which are behavioral traits not covered by annotations alone.

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 extremely concise—two brief sentences with zero waste. It front-loads the core purpose and efficiently adds critical usage detail about 'reveal', making every word earn its place without redundancy.

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 low schema coverage, the description is minimally adequate. It covers the tool's purpose and a key parameter behavior, but lacks details on return format, error conditions, or historical data scope, leaving the agent with incomplete context for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate but only partially does so. It explains the 'reveal' parameter's effect on returning passwords, but omits semantics for 'id' (e.g., what it refers to) and doesn't clarify parameter interactions or constraints, leaving significant gaps in understanding.

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 verb ('Get') and resource ('password history'), specifying it retrieves historical passwords for an item. It distinguishes from siblings like 'keychain_get_password' by focusing on history rather than current password, but doesn't explicitly contrast with all sibling get operations.

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 when password history is needed, with the 'reveal' parameter condition for returning passwords. However, it lacks explicit guidance on when to choose this over alternatives like 'keychain_get_item' or prerequisites for accessing history, leaving usage context partially implied.

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