Skip to main content
Glama

Create Note

keychain_create_note

Create secure notes in your Bitwarden vault to store sensitive information with customizable fields and organizational options.

Instructions

Create a secure note item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
notesNo
fieldsNo
favoriteNo
organizationIdNo
collectionIdsNo
folderIdNo

Implementation Reference

  • Tool registration for "keychain_create_note" calling SDK's createNote method.
      `${deps.toolPrefix}.create_note`,
      {
        title: 'Create Note',
        description: 'Create a secure note item.',
        inputSchema: {
          name: z.string(),
          notes: z.string().optional(),
          fields: z
            .array(
              z.object({
                name: z.string(),
                value: z.string(),
                hidden: z.boolean().optional(),
              }),
            )
            .optional(),
          favorite: z.boolean().optional(),
          organizationId: z.string().optional(),
          collectionIds: z.array(z.string()).optional(),
          folderId: z.string().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const created = await sdk.createNote(input);
        return {
          structuredContent: { item: created },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
  • Implementation of createNote method in KeychainSdk, which constructs a note and calls the Bitwarden CLI.
    async createNote(input: {
      name: string;
      notes?: string;
      fields?: ItemFieldInput[];
      reveal?: boolean;
      favorite?: boolean;
      organizationId?: string;
      collectionIds?: string[];
      folderId?: string;
    }): Promise<unknown> {
      return this.bw.withSession(async (session) => {
        if (this.syncOnWrite()) {
          await this.bw
            .runForSession(session, ['sync'], {
              timeoutMs: 120_000,
            })
            .catch(() => {});
        }
    
        const tpl = (await this.bw.getTemplateItemForSession(
          session,
        )) as AnyRecord;
        const item = deepClone(tpl);
        item.type = ITEM_TYPE.note;
        item.name = input.name;
        item.notes = input.notes ?? '';
        item.favorite = input.favorite ?? false;
        if (input.organizationId) item.organizationId = input.organizationId;
        if (input.folderId) item.folderId = input.folderId;
        if (!item.secureNote || typeof item.secureNote !== 'object') {
          item.secureNote = { type: 0 };
        }
        item.fields = normalizeFields(input.fields) ?? [];
        if (input.collectionIds) item.collectionIds = input.collectionIds;
    
        const encoded = encodeJsonForBw(item);
        const { stdout } = await this.bw.runForSession(
          session,
          ['create', 'item', encoded],
          { timeoutMs: 120_000 },
        );
        const created = this.parseBwJson<AnyRecord>(stdout);
    
        if (input.collectionIds?.length) {
          const encodedCols = encodeJsonForBw(input.collectionIds);
          await this.bw
            .runForSession(
              session,
              ['edit', 'item-collections', String(created.id), encodedCols],
              { timeoutMs: 120_000 },
            )
            .catch(() => {});
        }
    
        return this.maybeRedact(created, input.reveal);
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Create' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about permissions required, whether this is reversible/destructive, rate limits, authentication needs, or what happens on success/failure. It's minimally descriptive beyond the basic action.

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—a single four-word sentence with zero wasted words. It's front-loaded with the core action. While it may be too brief for completeness, it earns full marks for conciseness.

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 the complexity (7 parameters, no schema descriptions, no annotations, no output schema, many sibling tools), the description is severely incomplete. It doesn't explain what a 'secure note item' is, how it differs from other item types, what parameters are needed, what the tool returns, or any behavioral context. For a creation tool with many parameters, this is inadequate.

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

Parameters2/5

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

With 7 parameters and 0% schema description coverage, the schema provides no parameter documentation. The description adds no parameter semantics whatsoever—it doesn't mention any of the parameters (name, notes, fields, favorite, organizationId, collectionIds, folderId) or explain their purpose, format, or relationships. This leaves most parameters completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a secure note item' clearly states the verb ('Create') and resource ('secure note item'), which is better than a tautology. However, it doesn't distinguish this tool from its many siblings (e.g., keychain_create_card, keychain_create_login) beyond specifying it's for 'notes' rather than other item types. It's vague about what a 'secure note item' entails in this context.

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. With many sibling tools for creating different item types (e.g., cards, logins, folders), there's no indication of when a 'secure note' is appropriate versus other item types, nor any prerequisites or exclusions mentioned.

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