Skip to main content
Glama

Create Folder

keychain_create_folder

Create a personal folder in your Bitwarden vault to organize passwords and secure items by specifying a folder name.

Instructions

Create a Bitwarden folder (personal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • Handler implementation for creating a folder in Bitwarden, registered as 'create_folder'. Note that while the prompt referred to 'keychain_create_folder', the actual registration in this codebase uses the 'create_folder' suffix under the tool prefix.
    registerTool(
      `${deps.toolPrefix}.create_folder`,
      {
        title: 'Create Folder',
        description: 'Create a Bitwarden folder (personal).',
        inputSchema: {
          name: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const folder = await sdk.createFolder({ name: input.name });
        return {
          structuredContent: { folder },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool creates a folder but doesn't mention permissions required, whether it's idempotent, error conditions (e.g., duplicate names), or what happens on success (e.g., returns a folder ID). For a mutation tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, 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.

Completeness2/5

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

Given the tool's complexity (a mutation operation), lack of annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error handling, leaving significant gaps for an AI agent to use it correctly.

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?

The input schema has one parameter ('name') with 0% description coverage, and the tool description doesn't add any parameter details (e.g., format, constraints, or examples). Since there's only one parameter, the baseline is 4, but the description fails to compensate for the lack of schema documentation, reducing the score to 3.

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') and resource ('Bitwarden folder') with the qualifier '(personal)', which distinguishes it from organizational folders. However, it doesn't explicitly differentiate from sibling tools like 'keychain_edit_folder' or 'keychain_delete_folder', though the verb 'Create' implies a distinct operation.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., authentication), when not to use it (e.g., for organizational folders), or refer to sibling tools like 'keychain_edit_folder' for modifications. The description lacks context for decision-making.

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