Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create Note

keychain_create_note

Create a secure note for free-form text and secrets that don't fit into login, card, identity, or SSH key items. Add custom fields, organize by folder/collection, and get redacted summaries by default.

Instructions

Create a secure note item. Use this for free-form text or secrets that do not belong in a login, card, identity, or SSH key item. Accepts custom fields plus folder/organization/collection scoping, and returns a redacted item summary by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the secure note item.
notesNoOptional note text stored on the item.
fieldsNoCustom fields to store on the item. Hidden fields are redacted in summaries.
favoriteNoMark the item as a favorite when true.
folderIdNoPersonal folder id, not an organization collection id.
collectionIdsNoBitwarden collection ids, not folder ids.
organizationIdNoBitwarden organization id; used for org-scoped collection operations.

Schema Changelog

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

  1. Changed11 schema fields changedv0.2.19
    • addedInput schema / properties / collectionIds / description
      Added value: +"Bitwarden collection ids, not folder ids."
    • addedInput schema / properties / favorite / description
      Added value: +"Mark the item as a favorite when true."
    • addedInput schema / properties / fields / description
      Added value: +"Custom fields to store on the item. Hidden fields are redacted in summaries."
    • addedInput schema / properties / fields / items / description
      Added value: +"Custom field stored on the item."
    • addedInput schema / properties / fields / items / properties / hidden / description
      Added value: +"Hide the field value in summaries when true."
    • addedInput schema / properties / fields / items / properties / name / description
      Added value: +"Custom field name stored on the item."
    • addedInput schema / properties / fields / items / properties / value / description
      Added value: +"Custom field value stored on the item."
    • addedInput schema / properties / folderId / description
      Added value: +"Personal folder id, not an organization collection id."
    • addedInput schema / properties / name / description
      Added value: +"Display name for the secure note item."
    • addedInput schema / properties / notes / description
      Added value: +"Optional note text stored on the item."
    • addedInput schema / properties / organizationId / description
      Added value: +"Bitwarden organization id; used for org-scoped collection operations."
  2. Addedv0.1.20

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive. Description adds behavioral context: returns a redacted item summary by default. No contradiction.

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, front-loaded with purpose and usage, then features and return behavior. No wasted words.

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 purpose, usage, accepted parameters, and return value despite no output schema. Parameter count and schema descriptions are sufficient. Minor omission: no error or idempotency info, but acceptable for a create tool.

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 coverage is 100%, so baseline is 3. Description summarizes parameters (custom fields, scoping) but adds no new semantic detail beyond schema.

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 secure note item and distinguishes from siblings by listing what it is not for (login, card, identity, SSH key). Verb and resource are specific.

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 to use for free-form text or secrets that do not belong in other item types, implying alternatives. Does not name sibling tools directly but gives clear use case.

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