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

bitwarden-agent-vault-mcp

by ceweldy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Find Bitwarden secrets

list_secrets
Read-only

Retrieves a list of secret names and metadata, with optional filtering by project or search query, without exposing secret values.

Instructions

List secret names and metadata, optionally filtered by project or search text. Values are never returned by this tool.

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": "list_secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate read-only and open-world hints. The description adds that secret values are never returned, a crucial behavioral trait. It does not address pagination or result completeness, but annotations cover the safety profile.

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?

Two sentences, immediate action verb, no fluff. Perfectly concise for its purpose.

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?

The description lacks explanation of what 'metadata' includes, how filters combine, and implications of openWorldHint. No output schema exists to clarify return structure. Overall, leaves some information gaps.

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 provides no descriptions for the two optional parameters. The description mentions they enable filtering by project or search text, adding high-level meaning but lacking details on format or combination behavior.

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 it lists secret names and metadata, differentiating from get_secret which returns values. The verb 'list' and resource 'secrets' are explicit, and sibling tools provide context.

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 explains optional filters by project or search text, implying use for metadata browsing rather than retrieving secret values. However, it does not explicitly name alternatives like get_secret for when values are needed.

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