Skip to main content
Glama

Create Identity

keychain_create_identity

Create identity items in a Bitwarden vault to store personal information like names, addresses, and contact details for secure management.

Instructions

Create an identity item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
identityNo
notesNo
fieldsNo
favoriteNo
organizationIdNo
collectionIdsNo
folderIdNo

Implementation Reference

  • The tool 'keychain_create_identity' is registered and implemented in src/tools/registerTools.ts. It calls the `sdk.createIdentity` method.
      `${deps.toolPrefix}.create_identity`,
      {
        title: 'Create Identity',
        description: 'Create an identity item.',
        inputSchema: {
          name: z.string(),
          identity: z
            .object({
              title: z.string().optional(),
              firstName: z.string().optional(),
              middleName: z.string().optional(),
              lastName: z.string().optional(),
              address1: z.string().optional(),
              address2: z.string().optional(),
              address3: z.string().optional(),
              city: z.string().optional(),
              state: z.string().optional(),
              postalCode: z.string().optional(),
              country: z.string().optional(),
              company: z.string().optional(),
              email: z.string().optional(),
              phone: z.string().optional(),
              ssn: z.string().optional(),
              username: z.string().optional(),
              passportNumber: z.string().optional(),
              licenseNumber: z.string().optional(),
            })
            .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(),
          organizationId: z.string().optional(),
          collectionIds: z.array(z.string()).optional(),
          folderId: z.string().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const created = await sdk.createIdentity(input);
        return {
          structuredContent: { item: created },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Create an identity item' implies a write/mutation operation but provides no information about permissions required, whether the creation is permanent, what happens on failure, rate limits, or any other behavioral characteristics. This is completely inadequate for a tool that creates sensitive identity data.

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 maximally concise with a single four-word sentence. However, this conciseness comes at the cost of being severely under-specified rather than efficiently informative.

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 tool that creates sensitive identity data with 8 parameters (including a complex nested object), no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It provides no context about what the tool actually does, how to use it properly, or what to expect from it.

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 8 parameters and 0% schema description coverage, the description provides no information about any parameters. It doesn't mention the required 'name' parameter or explain the complex 'identity' object structure with 17 sub-properties. The description fails to compensate for the complete lack of schema 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 identity item' is essentially a tautology that restates the tool name and title without adding meaningful specificity. It doesn't explain what an 'identity item' is in this context or differentiate this tool from sibling creation tools like keychain_create_card or keychain_create_login.

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?

The description provides absolutely no guidance about when to use this tool versus alternatives. With multiple sibling creation tools (keychain_create_card, keychain_create_login, etc.), there's no indication of what distinguishes an 'identity item' from other item types or when this specific creation tool is appropriate.

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