Skip to main content
Glama
Sign In
bitwarden-agent-vault-mcp

bitwarden-agent-vault-mcp

by ceweldy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Check Bitwarden Agent Vault MCP

status
Read-only

Verify local CLI installation and machine-token availability, with optional live Bitwarden access check, without credential exposure.

Instructions

Check local CLI installation, machine-token availability, and optional live Bitwarden access without exposing credentials.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault
verify_remoteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, signaling a safe read operation. The description adds value by specifying exactly what is checked (installation, token, live access) and reassures that credentials are not exposed, providing behavioral context beyond annotations.

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, concise sentence that front-loads the main purpose with no unnecessary words. Every part earns its place.

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

Completeness4/5

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

Given the tool's simplicity (one boolean parameter, no output schema, strong annotations), the description covers the core functionality and safety. It lacks return format details, but for a low-complexity tool, it is sufficiently complete.

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 description must compensate. The description implies the 'verify_remote' boolean parameter controls optional live access, but it does not explicitly link the parameter name or its effect. The added meaning is moderate.

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 clearly states the tool checks local CLI installation, machine-token availability, and optional live Bitwarden access, using a specific verb and distinct resources. It differentiates from sibling tools like get_secret or list_secrets by focusing on environment readiness rather than data retrieval.

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 this tool is for verifying setup before using other tools, but it does not explicitly state when to use it or provide alternatives. Without explicit when-not or usage context, the guidance is adequate but not strong.

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

Deploy Server

Other Tools