Skip to main content
Glama

Create SSH Key

keychain_create_ssh_key

Create and store SSH key pairs as secure notes in a Bitwarden vault for secure access management.

Instructions

Create an SSH key object (stored as secure note with fields).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
publicKeyYes
privateKeyYes
fingerprintNo
commentNo
notesNo
favoriteNo
organizationIdNo
collectionIdsNo
folderIdNo

Implementation Reference

  • Tool registration and handler for 'keychain_create_ssh_key' (prefixed).
      `${deps.toolPrefix}.create_ssh_key`,
      {
        title: 'Create SSH Key',
        description:
          'Create an SSH key object (stored as secure note with fields).',
        inputSchema: {
          name: z.string(),
          publicKey: z.string(),
          privateKey: z.string(),
          fingerprint: z.string().optional(),
          comment: z.string().optional(),
          notes: z.string().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.createSshKey(input);
        return {
          structuredContent: { item: created },
          content: [{ type: 'text', text: 'Created.' }],
        };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions storage as a 'secure note with fields,' hinting at data persistence, but lacks critical behavioral details like authentication requirements, mutation effects (e.g., overwriting existing keys), rate limits, or error handling for a tool that creates sensitive SSH keys.

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. It avoids redundancy but could be slightly more informative without sacrificing brevity.

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

Completeness2/5

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

Given the complexity (10 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain parameter meanings, behavioral traits, or output expectations, leaving significant gaps for a tool that creates sensitive SSH key objects.

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?

Schema description coverage is 0%, so the description must compensate. It only vaguely references 'fields' without explaining any of the 10 parameters (e.g., what 'name', 'publicKey', or 'collectionIds' mean). This adds minimal semantic value beyond the schema's structure.

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 ('Create') and resource ('SSH key object'), specifying it's stored as a secure note with fields. It distinguishes from siblings like 'keychain_create_login' or 'keychain_create_note' by focusing on SSH keys, but doesn't explicitly contrast with similar creation tools.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling creation tools (e.g., keychain_create_login, keychain_create_note), the description lacks context about prerequisites, appropriate scenarios, or exclusions, leaving usage 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