Skip to main content
Glama

Edit Org Collection

keychain_edit_org_collection

Rename an organization collection in a Bitwarden vault to update its label for better organization and access control.

Instructions

Rename an organization collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes
idYes
nameYes

Implementation Reference

  • The tool 'keychain_edit_org_collection' is registered in 'src/tools/registerTools.ts'. Its handler uses the 'keychainSdk' to execute the 'editOrgCollection' method.
      `${deps.toolPrefix}.edit_org_collection`,
      {
        title: 'Edit Org Collection',
        description: 'Rename an organization collection.',
        inputSchema: {
          organizationId: z.string(),
          id: z.string(),
          name: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const collection = await sdk.editOrgCollection(input);
        return {
          structuredContent: { collection },
          content: [{ type: 'text', text: 'Updated.' }],
        };
      },
    );
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 for behavioral disclosure. While 'Rename' implies a mutation operation, the description doesn't disclose whether this requires specific permissions, whether the rename is reversible, what happens to references to the old collection name, or any rate limits. 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 that states the core functionality without unnecessary words. It's appropriately sized for a simple rename operation and front-loads the essential information.

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 3 undocumented parameters, 0% schema description coverage, and no output schema, the description is insufficient. It doesn't explain what the parameters represent, what the tool returns, or any behavioral aspects like permissions or side effects. The agent would struggle to use this tool correctly without additional context.

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 all three parameters are undocumented in the schema. The description mentions 'Rename' which implies a 'name' parameter, but doesn't explain the purpose of 'organizationId' and 'id' parameters or provide any format/constraint details. The description adds minimal value beyond what can be inferred from the tool name.

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 target ('an organization collection'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'keychain_edit_folder' or 'keychain_update_item', which appear to perform similar edit/update operations on different resources.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or exclusions. With sibling tools like 'keychain_update_item' and 'keychain_edit_folder' available, the agent receives no help in choosing between them.

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