Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

List Organizations

keychain_list_organizations
Read-only

Retrieve available Bitwarden organizations for the current user to manage access permissions and vault structure.

Instructions

List organizations available to the current Bitwarden user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo
limitNo

Implementation Reference

  • src/tools/registerTools.ts:1462-1489 (handler)
    The tool `keychain_list_organizations` is registered in `src/tools/registerTools.ts`. The handler calls `sdk.listOrganizations(input)`. Note: The tool name used during registration is dynamically built, likely resolving to `keychain_list_organizations` based on the context of other tools.
        };
  },
);

registerTool(
  `${deps.toolPrefix}.create_card`,
  {
    title: 'Create Card',
    description: 'Create a payment card item.',
    inputSchema: {
      name: z.string(),
      cardholderName: z.string().optional(),
      brand: z.string().optional(),
      number: z.string().optional(),
      expMonth: z.string().optional(),
      expYear: z.string().optional(),
      code: z.string().optional(),
      notes: z.string().optional(),
      fields: z
        .array(
          z.object({
            name: z.string(),
            value: z.string(),
            hidden: z.boolean().optional(),
          }),
        )
        .optional(),
      favorite: z.boolean().optional(),

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds minimal behavioral context beyond this, specifying that it lists organizations 'available to the current Bitwarden user,' which implies scope but does not detail aspects like pagination, rate limits, or authentication needs. 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 a single, clear sentence that efficiently conveys the core functionality without unnecessary details. It is front-loaded and wastes no words, making it easy to parse and understand quickly.

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?

Given the tool's low complexity (a read-only list operation with 2 optional parameters), no output schema, and annotations covering safety, the description is adequate but incomplete. It lacks details on parameter usage, output format, or error handling, which could aid an AI agent in proper invocation, though the simplicity of the tool mitigates some gaps.

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?

With 0% schema description coverage, the input schema lacks descriptions for the 'search' and 'limit' parameters. The description does not mention these parameters at all, failing to compensate for the schema gap. However, since there are only 2 parameters and the tool's purpose is straightforward, the baseline score of 3 is applied as it minimally meets expectations without adding value.

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 ('List') and resource ('organizations available to the current Bitwarden user'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'keychain_get_organization' or 'keychain_list_org_collections', which might offer similar or overlapping functionality.

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, such as 'keychain_get_organization' for retrieving a single organization or 'keychain_list_org_collections' for listing collections within organizations. It lacks explicit context or exclusions, leaving usage decisions ambiguous.

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