Skip to main content
Glama

Get Item

keychain_get_item
Read-only

Retrieve a specific vault item from your Bitwarden or Vaultwarden password manager by its unique identifier, with options to reveal or redact sensitive data.

Instructions

Get a vault item by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
revealNo

Implementation Reference

  • The implementation of getItem in KeychainSdk, which corresponds to the keychain_get_item tool.
    async getItem(id: string, opts: { reveal?: boolean } = {}): Promise<unknown> {
      const item = await this.bw.withSession(async (session) => {
        const { stdout } = await this.bw.runForSession(
          session,
          ['get', 'item', id],
          { timeoutMs: 60_000 },
        );
        return this.parseBwJson(stdout);
      });
    
      return this.maybeRedact(item, opts.reveal);
    }
  • Registration of the tool keychain_get_item (referred to as .get_item in the code).
    registerTool(
      `${deps.toolPrefix}.get_item`,
      {
        title: 'Get Item',
        description: 'Get a vault item by id.',
        annotations: { readOnlyHint: true },
        inputSchema: {
          id: z.string(),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const item = await sdk.getItem(input.id, {
          reveal: effectiveReveal(input),
        });
        return {
          structuredContent: { item },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds minimal behavioral context beyond this—it specifies retrieval by ID but doesn't mention authentication needs, rate limits, or what happens if the ID doesn't exist. No contradiction with annotations exists.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for a simple retrieval tool.

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 the annotations cover safety (read-only) and the tool has only 2 parameters, the description is minimally adequate. However, with no output schema and incomplete parameter explanation (especially for 'reveal'), it leaves gaps in understanding the full tool behavior and response format.

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?

With 0% schema description coverage, the schema provides no parameter documentation. The description mentions 'by id', which clarifies the purpose of the required 'id' parameter, but doesn't explain the optional 'reveal' parameter at all. This partial compensation justifies a baseline score.

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') and resource ('vault item by id'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar siblings like 'keychain_get_attachment' or 'keychain_get_folder', which also retrieve specific items by ID.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. With siblings like 'keychain_search_items' for broader queries and 'keychain_get_password' for specific field retrieval, the description offers no context about selection criteria or prerequisites.

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