Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send Create

keychain_send_create

Create a Bitwarden Send for text or file content, with optional password protection, access limits, and expiration.

Instructions

Quick-create a Bitwarden Send through bw send. Use type=text with text, or type=file with filename plus contentBase64; deleteInDays controls expiration deletion, maxAccessCount limits accesses, password protects the Send, and emails grant email-gated access. For advanced JSON templates or edits, use send_create_encoded and send_edit instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional Send display name.
textNoText content for type=text Sends.
typeYesSend payload type: text uses text; file uses filename plus contentBase64.
notesNoOptional private notes on the Send.
emailsNoRecipient email addresses for Bitwarden Send email-gated access. Mutually exclusive with password; callers still need to share the Send URL.
hiddenNoHide text Send content by default when recipients open it.
filenameNoVisible filename required with contentBase64 for file sends.
passwordNoOptional Send access password required by recipients.
fullObjectNoAsk bw send to return the full Send object when supported.
deleteInDaysNoDays until Bitwarden automatically deletes the Send (1-3650).
contentBase64NoBase64-encoded file bytes for file sends, not a filesystem path.
maxAccessCountNoMaximum number of Send accesses before it becomes unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.37
    • changedInput schema / properties / emails / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changedv0.2.26
    • addedInput schema / properties / emails
      Added value: +{
+  "description": "Recipient email addresses for Bitwarden Send email-gated access. Mutually exclusive with password; callers still need to share the Send URL.",
+  "items": {
+    "format": "email",
+    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}
  3. Changed11 schema fields changedv0.2.19
    • addedInput schema / properties / contentBase64 / description
      Added value: +"Base64-encoded file bytes for file sends, not a filesystem path."
    • addedInput schema / properties / deleteInDays / description
      Added value: +"Days until Bitwarden automatically deletes the Send (1-3650)."
    • addedInput schema / properties / filename / description
      Added value: +"Visible filename required with contentBase64 for file sends."
    • addedInput schema / properties / fullObject / description
      Added value: +"Ask bw send to return the full Send object when supported."
    • addedInput schema / properties / hidden / description
      Added value: +"Hide text Send content by default when recipients open it."
    • addedInput schema / properties / maxAccessCount / description
      Added value: +"Maximum number of Send accesses before it becomes unavailable."
    • addedInput schema / properties / name / description
      Added value: +"Optional Send display name."
    • addedInput schema / properties / notes / description
      Added value: +"Optional private notes on the Send."
    • addedInput schema / properties / password / description
      Added value: +"Optional Send access password required by recipients."
    • addedInput schema / properties / text / description
      Added value: +"Text content for type=text Sends."
    • addedInput schema / properties / type / description
      Added value: +"Send payload type: text uses text; file uses filename plus contentBase64."
  4. Addedv0.1.20

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive operation. The description adds behavioral context beyond those flags: expiration is driven by deleteInDays, access is capped by maxAccessCount, password protection and email-gated access are supported. No contradiction with annotations.

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 dense sentences with the purpose front-loaded, the type-conditional guidance in the middle, and the alternative-tool routing at the end. No filler and no unnecessary repetition of the already-complete schema.

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

Completeness5/5

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

For a creation tool with a fully documented 12-parameter schema, the description supplies the essential selection rules, key access/expiration behaviors, and the advanced alternative. Nothing needed to invoke the tool correctly is missing, even without an output schema.

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 100%, so the baseline is 3. The description condenses the type-to-field relationship and option purposes, but it mostly restates what the schema already documents rather than adding new semantic meaning.

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 opens with 'Quick-create a Bitwarden Send through bw send', naming a specific verb, resource, and workflow. It clearly differentiates this tool from send_create_encoded and send_edit by framing it as the quick/simple path for directly-typed payloads.

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

Usage Guidelines5/5

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

It gives concrete type-specific usage ('type=text with text, or type=file with filename plus contentBase64') and an explicit when-not-to-use rule: 'For advanced JSON templates or edits, use send_create_encoded and send_edit instead.' This routes the agent correctly without needing sibling schemas.

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