Skip to main content
Glama

Send Edit (Encoded JSON)

keychain_send_edit

Edit Bitwarden secure file or text shares by providing JSON data or base64-encoded content, optionally specifying the item ID for targeted updates.

Instructions

Edit a Send via bw send edit. Provide encodedJson (base64) or json (will be bw-encoded). Optional: itemId (maps to --itemid).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
encodedJsonNo
jsonNo
itemIdNo

Implementation Reference

  • Registration and handler for the `send_edit` tool. It uses `sdk.sendEdit` to perform the operation.
      `${deps.toolPrefix}.send_edit`,
      {
        title: 'Send Edit (Encoded JSON)',
        description:
          'Edit a Send via `bw send edit`. Provide `encodedJson` (base64) or `json` (will be bw-encoded). Optional: `itemId` (maps to --itemid).',
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          openWorldHint: true,
        },
        inputSchema: {
          encodedJson: z.string().optional(),
          json: z.unknown().optional(),
          itemId: z.string().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const send = await sdk.sendEdit(input);
        return {
          structuredContent: { send },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

Annotations indicate this is a mutable, non-destructive tool (readOnlyHint: false, destructiveHint: false) with open-world data (openWorldHint: true). The description adds context about the encoding process ('bw-encoded'), but doesn't disclose behavioral traits like permissions, rate limits, or error handling 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the main action, using two sentences efficiently. It avoids unnecessary details, though it could be more structured in explaining parameter choices.

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

Completeness2/5

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

Given 3 parameters with 0% schema coverage, no output schema, and annotations covering only basic hints, the description is incomplete. It lacks details on return values, error cases, or how the editing process works, making it insufficient for a mutation tool in a complex sibling set.

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 schema provides no parameter details. The description explains that 'encodedJson' is base64 and 'json' will be bw-encoded, and 'itemId' maps to --itemid, adding some semantics. However, it doesn't fully compensate for the lack of schema descriptions, leaving gaps in understanding parameter usage or constraints.

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 ('Edit a Send') and the mechanism ('via bw send edit'), which is specific. It distinguishes from siblings like 'keychain_send_create' or 'keychain_send_delete' by focusing on editing, though it doesn't explicitly contrast with 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 guidance is provided on when to use this tool versus alternatives. It mentions optional parameters but doesn't specify scenarios, prerequisites, or exclusions, such as when to choose 'encodedJson' over 'json' or how it differs from other send-related tools.

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