Skip to main content
Glama

Create Org Collection

keychain_create_org_collection

Create a new collection within an organization's vault to organize and manage shared credentials and secure items for team access control.

Instructions

Create an organization collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYes
nameYes

Implementation Reference

  • Registration and handler for "keychain_create_org_collection". Note: In the codebase, it is registered with `deps.toolPrefix + '.create_org_collection'`.
      `${deps.toolPrefix}.create_org_collection`,
      {
        title: 'Create Org Collection',
        description: 'Create an organization collection.',
        inputSchema: {
          organizationId: 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.createOrgCollection(input);
        return {
          structuredContent: { collection },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
Behavior1/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. It only states the action ('create') without any details on permissions, side effects, error conditions, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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, straightforward sentence with no wasted words. It's appropriately sized for a simple tool, though its brevity contributes to the lack of detail in other dimensions.

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

Completeness1/5

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

For a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It lacks essential details on behavior, parameters, and usage, failing to provide the context needed for effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so parameters are undocumented in the schema. The description provides no information about the 'organizationId' or 'name' parameters, their formats, constraints, or examples. It fails to compensate for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create an organization collection' restates the tool name and title almost verbatim, making it tautological. It specifies the action ('create') and resource ('organization collection'), but doesn't differentiate from sibling tools like 'keychain_create_folder' or 'keychain_create_collection' beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There's no mention of prerequisites, context, or comparisons to sibling tools like 'keychain_create_folder' or 'keychain_create_collection', leaving the agent with no 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