Skip to main content
Glama

Send Remove Password

keychain_send_remove_password
Destructive

Remove saved passwords from Bitwarden Send items to enhance security by eliminating stored credentials after sharing.

Instructions

Remove a Send's saved password (bw send remove-password).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler for the tool "keychain_send_remove_password" is registered in `src/tools/registerTools.ts`. It uses the `sendRemovePassword` method from the injected `sdk` to perform the action.
      `${deps.toolPrefix}.send_remove_password`,
      {
        title: 'Send Remove Password',
        description: "Remove a Send's saved password (bw send remove-password).",
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          openWorldHint: true,
        },
        inputSchema: {
          id: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const result = await sdk.sendRemovePassword(input);
        return {
          structuredContent: { result },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior4/5

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

Annotations indicate destructiveHint=true (mutation) and readOnlyHint=false (non-read-only), which align with 'Remove' in the description. The description adds context by specifying it targets 'saved password' rather than the Send itself, clarifying scope. However, it doesn't mention side effects (e.g., if the Send becomes inaccessible) or authentication needs beyond what annotations provide.

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 no redundant words. It front-loads the core action ('Remove a Send's saved password') and includes a concise parenthetical for technical context, making it easy to parse.

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?

For a destructive tool with no output schema and low schema coverage, the description is minimal but functional. It covers the basic purpose and parameter intent, but lacks details on behavior (e.g., error cases, confirmation prompts) and doesn't fully compensate for the missing parameter documentation, leaving room for ambiguity.

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%, with one parameter 'id' undocumented in the schema. The description implies 'id' refers to a Send (from 'a Send's saved password'), adding semantic meaning. However, it doesn't specify the ID format or source, leaving gaps in parameter understanding.

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 ('Remove') and the resource ('a Send's saved password'), with the parenthetical 'bw send remove-password' providing additional context. It distinguishes from siblings like 'keychain_send_delete' (deletes the entire Send) or 'keychain_send_edit' (modifies Send properties), but doesn't explicitly contrast them.

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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., the Send must exist, user must have permission), nor does it clarify scenarios where removing a password is appropriate versus editing or deleting the Send entirely.

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