Skip to main content
Glama

Vault Status

keychain_status
Read-only

Check Bitwarden CLI status to verify if the vault is locked or unlocked, and view server and user information for secure password management.

Instructions

Returns Bitwarden CLI status (locked/unlocked, server, user).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool is registered as `.status` but is functionally equivalent to `keychain_status` in terms of providing vault status. The implementation delegates to `sdk.status()`.
    registerTool(
      `${deps.toolPrefix}.status`,
      {
        title: 'Vault Status',
        description:
          'Returns Bitwarden CLI status (locked/unlocked, server, user).',
        annotations: { readOnlyHint: true },
        inputSchema: {},
        _meta: toolMeta,
      },
      async (_input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const status = await sdk.status();
        const summary =
          status &&
          typeof status === 'object' &&
          typeof (status as { summary?: unknown }).summary === 'string'
            ? String((status as { summary?: unknown }).summary)
            : 'Vault access ready.';
        return {
          structuredContent: { status },
          content: [{ type: 'text', text: summary }],
        };
      },
    );
Behavior3/5

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

The description adds minimal behavioral context beyond annotations. Annotations indicate readOnlyHint=true, confirming it's a safe read operation. The description specifies what status information is returned (locked/unlocked, server, user), which is useful but doesn't cover other traits like error handling, rate limits, or authentication needs. 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: 'Returns Bitwarden CLI status (locked/unlocked, server, user).' It's front-loaded with the core purpose and includes essential details in parentheses, with no wasted words. Every part 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?

Given the tool's simplicity (0 parameters, read-only annotation, no output schema), the description is adequate but has gaps. It explains what status is returned, but lacks details on format (e.g., structured data vs. plain text), error cases, or dependencies. For a status-checking tool, this is minimally viable but could be more informative.

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?

The tool has 0 parameters, with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, so it meets the baseline of 4. It appropriately focuses on the tool's output semantics instead.

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 tool's purpose: 'Returns Bitwarden CLI status (locked/unlocked, server, user).' It specifies the verb ('Returns') and resource ('Bitwarden CLI status') with details on what status information is provided. However, it doesn't explicitly differentiate from sibling tools like 'keychain_get_organization' or 'keychain_get_username', which are also read operations but for specific data rather than overall CLI status.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the CLI must be initialized), exclusions, or comparisons to sibling tools like 'keychain_get_organization' for server details or 'keychain_get_username' for user info. Usage is implied only by the purpose statement.

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