Skip to main content
Glama

Get Organization

keychain_get_organization
Read-only

Retrieve organization details from a Bitwarden vault by specifying its unique identifier.

Instructions

Get an organization by id (bw get organization).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler and registration for 'keychain_get_organization'. Based on the `toolPrefix` logic, this registers as '{prefix}.get_organization'.
    registerTool(
      `${deps.toolPrefix}.get_organization`,
      {
        title: 'Get Organization',
        description: 'Get an organization by id (bw get organization).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          id: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const organization = await sdk.getOrganization(input);
        return {
          structuredContent: { organization },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds that it retrieves 'by id', which is useful context beyond annotations. However, it lacks details on error handling (e.g., if ID is invalid), permissions, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. The parenthetical '(bw get organization)' is slightly redundant but not wasteful. It could be more structured (e.g., separating usage notes), but it's appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a simple read tool with annotations covering safety, the description is minimally complete. It lacks output details (no schema), error handling, and sibling differentiation, but the core function is clear. Given the low complexity and annotation support, it's adequate but leaves room for improvement.

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?

Schema description coverage is 0%, so the schema alone documents the 'id' parameter without descriptions. The description mentions 'by id', adding minimal semantic context (it's an identifier for lookup). It doesn't specify format (e.g., UUID) or examples, leaving gaps. With one parameter and low coverage, this is adequate but not compensatory.

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 ('organization'), and specifies it's retrieved 'by id'. It distinguishes from siblings like 'keychain_list_organizations' by focusing on a single entity rather than listing. However, it doesn't fully differentiate from other 'get' tools like 'keychain_get_item' or 'keychain_get_folder' beyond the resource type.

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 (e.g., needing an organization ID), contrast with 'keychain_list_organizations' for browsing, or specify use cases. The parenthetical '(bw get organization)' is a command reference but not a usage guideline.

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