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

bitwarden-agent-vault-mcp

by ceweldy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Reveal a Bitwarden secret

get_secret
Read-only

Retrieves a plaintext secret by UUID or exact key when plaintext reveal is enabled.

Instructions

Return one secret value in plaintext by UUID or exact key when private configuration explicitly enables plaintext reveal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "get_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

The description adds value beyond the readOnlyHint annotation by revealing that the tool returns plaintext and that a configuration gate exists. It does not cover error behavior or rate limits, but for a simple read operation the transparency is good.

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?

A single sentence of 18 words that is front-loaded and contains no redundancy. Every word serves a purpose.

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?

The tool is simple with no output schema. The description explains the core action and a critical condition. Missing details on error responses or return format, but overall adequate for the tool's simplicity.

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?

With 0% schema description coverage, the description provides crucial meaning for the identifier parameter (UUID or exact key). However, it fails to explain the purpose of the project_id parameter, leaving a gap.

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 returns a secret value in plaintext by UUID or exact key, with a conditional on configuration. This specific verb-resource pairing distinguishes it from siblings like list_secrets (metadata) and store_secret (write).

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

Usage Guidelines4/5

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

The description includes a key prerequisite (configuration must allow plaintext reveal) and specifies how to identify the secret (UUID or exact key). However, it does not explicitly advise when not to use or mention alternatives like run_with_secrets for cases where plaintext reveal is not enabled.

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