Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Send Create (Encoded JSON)

keychain_send_create_encoded

Create Bitwarden Sends with advanced template-level fields using encoded JSON, raw JSON, or direct text/file inputs. Encode and submit Send data when quick-create options are insufficient.

Instructions

Create a Send with the advanced bw send create flow. Provide an encodedJson template or raw json to encode, or create directly from text/file fields; file uses filename plus contentBase64 and hidden only affects text Sends. Use this when you need template-level fields beyond the quick send_create options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoDirect file payload alternative using filename and contentBase64.
jsonNoRaw Send JSON template; the server encodes it before bw send create.
textNoDirect text payload alternative to encodedJson/json.
hiddenNoHide direct text Send content by default when true.
encodedJsonNoBase64-encoded Send JSON template passed to bw send create.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv0.2.19
    • addedInput schema / properties / encodedJson / description
      Added value: +"Base64-encoded Send JSON template passed to bw send create."
    • addedInput schema / properties / file / description
      Added value: +"Direct file payload alternative using filename and contentBase64."
    • addedInput schema / properties / file / properties / contentBase64 / description
      Added value: +"Base64-encoded file bytes, not a filesystem path."
    • addedInput schema / properties / file / properties / filename / description
      Added value: +"Visible attachment or send filename stored in Bitwarden metadata."
    • addedInput schema / properties / hidden / description
      Added value: +"Hide direct text Send content by default when true."
    • addedInput schema / properties / json / description
      Added value: +"Raw Send JSON template; the server encodes it before bw send create."
    • addedInput schema / properties / text / description
      Added value: +"Direct text payload alternative to encodedJson/json."
  2. Addedv0.1.20

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate non-readOnly and non-destructive. Description adds that file uses contentBase64 (not filesystem), but does not detail side effects, permissions needed, or error behavior.

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, no unnecessary words, front-loaded with action and then usage condition. Efficient and clear.

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

Completeness4/5

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

Covers main input methods and sibling differentiation, but lacks mention of return value (e.g., created Send ID) and any validation constraints, given no output schema. Almost complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds value by clarifying the three input methods (encodedJson, json, text/file), the relationship between hidden and text, and that file's contentBase64 is not a path.

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?

Clearly states it creates a Send using advanced flow, distinguishes from quick send_create sibling by noting it supports template-level fields.

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?

Explicitly says when to use (for template-level fields beyond quick options). Provides brief usage hints for file and hidden fields, but doesn't specify when to avoid or list alternatives beyond quick send_create.

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