Skip to main content
Glama

Get Org Collection

keychain_get_org_collection
Read-only

Retrieve a specific organizational collection from a Bitwarden vault using its unique identifier to access grouped secure items.

Instructions

Get an org collection by id (bw get org-collection).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
organizationIdNo

Implementation Reference

  • Tool registration and handler implementation for keychain_get_org_collection.
      `${deps.toolPrefix}.get_org_collection`,
      {
        title: 'Get Org Collection',
        description: 'Get an org collection by id (bw get org-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.getOrgCollection(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 annotations. Annotations provide readOnlyHint=true, indicating a safe read operation. The description confirms this with 'Get', aligning with annotations. However, it doesn't disclose additional traits like error conditions, authentication needs, or rate limits. No contradiction with annotations exists.

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's front-loaded with the core purpose. Every part earns its place, making it efficient for quick understanding.

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 has annotations (readOnlyHint) but no output schema and 0% schema description coverage, the description is incomplete. It lacks details on return values, error handling, and parameter semantics, leaving gaps for a tool with 2 parameters. More context is needed for 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'by id', which corresponds to the 'id' parameter, but doesn't explain the 'organizationId' parameter or provide any semantic details about format, constraints, or relationships between parameters. This leaves half the parameters undocumented.

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 ('org collection'), and specifies it's retrieved 'by id'. It distinguishes from sibling tools like 'keychain_list_org_collections' by focusing on a single item retrieval rather than listing. However, it doesn't explicitly differentiate from other 'get' tools like 'keychain_get_collection' or 'keychain_get_organization'.

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 doesn't mention prerequisites, when not to use it, or compare it to similar tools like 'keychain_get_collection' or 'keychain_get_organization'. The only implied usage is needing an 'id', but this is already in the schema.

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