Skip to main content
Glama

Create Card

keychain_create_card

Create a payment card entry in your Bitwarden vault to store cardholder name, number, expiration, and security code securely.

Instructions

Create a payment card item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
cardholderNameNo
brandNo
numberNo
expMonthNo
expYearNo
codeNo
notesNo
fieldsNo
favoriteNo
organizationIdNo
collectionIdsNo
folderIdNo

Implementation Reference

  • The registration and handler implementation for the `keychain_create_card` (or prefixed version thereof) tool within `src/tools/registerTools.ts`.
      `${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(),
          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.createCard(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 burden for behavioral disclosure but offers none. It doesn't mention that this is a write/mutation operation, what permissions are required, whether it's idempotent, what happens on success/failure, or any side effects. For a tool that creates sensitive payment card data, this lack of behavioral information is critical.

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 at just four words. While this represents under-specification rather than ideal conciseness, within the scoring framework it earns full points for having zero wasted words and being front-loaded with the essential action. Every word serves a purpose, even if that purpose is minimally fulfilled.

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 with 13 parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what a 'payment card item' is in this system's context, doesn't cover any parameters, provides no behavioral context, and offers no guidance on usage. The description fails to provide the necessary context for proper tool invocation.

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 13 parameters and 0% schema description coverage, the description provides no parameter information whatsoever. It doesn't mention any of the 13 parameters by name, explain what 'name' (the only required parameter) should contain, clarify the purpose of optional fields like 'organizationId' or 'collectionIds', or provide examples. 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.

Purpose3/5

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

The description 'Create a payment card item' clearly states the verb ('Create') and resource ('payment card item'), but it's vague about what a 'payment card item' entails and doesn't distinguish this tool from sibling creation tools like keychain_create_login or keychain_create_note. It provides basic purpose but lacks specificity about the domain (password manager/vault) or how this differs from other item types.

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 zero guidance on when to use this tool versus alternatives. With many sibling tools including other creation tools (login, note, folder, etc.) and related tools like keychain_update_item, there's no indication of when this specific card creation tool is appropriate, what prerequisites exist, or when other tools might be better suited.

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