Skip to main content
Glama

Send Create (Encoded JSON)

keychain_send_create_encoded

Create secure Bitwarden Send items using base64-encoded JSON or raw JSON input, with options for text notes, hidden content, or file attachments.

Instructions

Create a Send via bw send create. Provide encodedJson (base64) or json (will be bw-encoded). Optional: text, hidden, or file (filename+contentBase64).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
encodedJsonNo
jsonNo
textNo
hiddenNo
fileNo

Implementation Reference

  • The tool 'keychain_send_create_encoded' is registered in 'src/tools/registerTools.ts'. Its handler invokes 'sdk.sendCreateEncoded'.
      `${deps.toolPrefix}.send_create_encoded`,
      {
        title: 'Send Create (Encoded JSON)',
        description:
          'Create a Send via `bw send create`. Provide `encodedJson` (base64) or `json` (will be bw-encoded). Optional: `text`, `hidden`, or `file` (filename+contentBase64).',
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          openWorldHint: true,
        },
        inputSchema: {
          encodedJson: z.string().optional(),
          json: z.unknown().optional(),
          text: z.string().optional(),
          hidden: z.boolean().optional(),
          file: z
            .object({
              filename: z.string(),
              contentBase64: z.string(),
            })
            .optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const send = await sdk.sendCreateEncoded(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 non-read-only, non-destructive, open-world operation. The description adds that it creates a Send via a specific command (`bw send create`), which provides implementation context. However, it doesn't disclose behavioral traits like rate limits, authentication needs, or error handling beyond what annotations cover, leaving gaps for a mutation tool.

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 extremely concise—two sentences with zero wasted words. It front-loads the core purpose and efficiently lists parameter options, making it easy to scan and understand quickly.

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?

Given 5 parameters with 0% schema coverage, no output schema, and annotations covering basic safety, the description provides essential parameter explanations but lacks details on return values, error cases, or usage examples. It's minimally adequate for a mutation tool but leaves significant context gaps for proper agent invocation.

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. It explains that 'encodedJson' is base64 and 'json' will be bw-encoded, and clarifies optional parameters ('text', 'hidden', 'file' with filename+contentBase64). This adds meaningful semantics beyond the bare schema, but doesn't detail all parameter interactions or constraints, leaving some ambiguity.

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 ('Create a Send') and the mechanism ('via `bw send create`'), which is specific and actionable. It distinguishes from sibling tools like 'keychain_send_create' by specifying the encoded JSON input format, though it doesn't explicitly contrast with all other 'create' tools (e.g., 'keychain_create_login').

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions the sibling tool 'keychain_send_create' implicitly through the command reference, but doesn't explain when to choose encoded JSON input over other methods or tools. No prerequisites, exclusions, or explicit alternatives are stated.

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