Skip to main content
Glama

Get Collection

keychain_get_collection
Read-only

Retrieve a specific Bitwarden collection by its ID to access grouped vault items. Use this tool to fetch collection details from your secure password manager.

Instructions

Get a collection by id (bw get collection).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
organizationIdNo

Implementation Reference

  • The implementation of `getCollection` which calls `bw get collection`.
    async getCollection(input: {
      id: string;
      organizationId?: string;
    }): Promise<unknown> {
      return this.bw.withSession(async (session) => {
        const args: string[] = ['get', 'collection', input.id];
        if (input.organizationId)
          args.push('--organizationid', input.organizationId);
        const { stdout } = await this.bw.runForSession(session, args, {
          timeoutMs: 60_000,
        });
        return this.parseBwJson(stdout);
      });
    }
  • The registration of the `get_collection` tool.
      `${deps.toolPrefix}.get_collection`,
      {
        title: 'Get Collection',
        description: 'Get a collection by id (bw get collection).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          id: z.string(),
          organizationId: z.string().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const collection = await sdk.getCollection(input);
        return {
          structuredContent: { collection },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

The description adds minimal behavioral context beyond the annotations. The annotation 'readOnlyHint: true' already indicates it's a safe read operation. The description implies retrieval by ID but does not disclose details like error handling, permissions, or rate limits. It does not contradict annotations, but provides little extra value.

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 sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence serves a purpose, earning its place efficiently.

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 lack of output schema and low parameter coverage, the description is insufficiently complete. It does not explain what a 'collection' is, what data is returned, or how parameters interact. For a tool with two parameters and no output schema, more context is needed to guide effective use.

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 0% schema description coverage, the description does not compensate by explaining parameters. It mentions 'id' implicitly but provides no details on format or usage. The 'organizationId' parameter is entirely undocumented, leaving semantics unclear. This falls short of the needed compensation for low schema coverage.

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 ('Get') and resource ('collection by id'), making the purpose understandable. It distinguishes from siblings like 'keychain_list_collections' by specifying retrieval of a single collection rather than listing multiple. However, it lacks specificity about what a 'collection' entails in this context, which slightly reduces clarity.

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. It does not mention prerequisites (e.g., authentication), differentiate from similar tools like 'keychain_get_org_collection', or specify contexts where it is appropriate. This leaves the agent without usage direction.

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