Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Edit Folder

keychain_edit_folder

Rename a personal Bitwarden folder by providing its ID and new name for organized vault management.

Instructions

Rename a Bitwarden folder (personal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes

Implementation Reference

  • src/tools/registerTools.ts:293-313 (handler)
    The implementation of the tool "keychain_edit_folder" (registered as edit_folder, potentially prefixed) in src/tools/registerTools.ts.
    registerTool(
  `${deps.toolPrefix}.edit_folder`,
  {
    title: 'Edit Folder',
    description: 'Rename a Bitwarden folder (personal).',
    inputSchema: {
      id: z.string(),
      name: z.string(),
    },
    _meta: toolMeta,
  },
  async (input, extra) => {
    if (isReadOnly) return readonlyBlocked();
    const sdk = await deps.getSdk(extra.authInfo);
    const folder = await sdk.editFolder(input);
    return {
      structuredContent: { folder },
      content: [{ type: 'text', text: 'Updated.' }],
    };
  },
);

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool renames folders, implying a mutation operation, but lacks details on permissions required, whether changes are reversible, error handling, or response format. This is insufficient for a mutation tool with zero annotation coverage.

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 is front-loaded with the core action and resource, making it easy to parse 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?

For a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, error cases, and output, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions renaming a folder, which implies 'name' is the new name, but doesn't explain 'id' (e.g., folder identifier) or provide any syntax, constraints, or examples. The description adds minimal value beyond the schema.

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 ('Rename') and resource ('a Bitwarden folder') with specificity. It adds the qualifier '(personal)' which distinguishes it from organizational folders, though it doesn't explicitly differentiate from sibling tools like 'keychain_edit_org_collection' beyond the personal scope.

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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, error conditions, or compare it to similar tools like 'keychain_edit_org_collection' for organizational folders, leaving usage context implied.

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