Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Identity

keychain_create_identity

Create a structured identity item for personal, contact, and address data, including custom fields and scoping. Sensitive fields are automatically redacted in summaries.

Instructions

Create an identity item. Use this for personal, contact, and address data instead of a login or card. Accepts structured identity fields plus custom fields and scoping, and returned summaries redact sensitive identity fields and hidden custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the identity item.
notesNoOptional note text stored on the item.
fieldsNoCustom fields to store on the item. Hidden fields are redacted in summaries.
favoriteNoMark the item as a favorite when true.
folderIdNoPersonal folder id, not an organization collection id.
identityNoStructured identity profile data to store on the item.
collectionIdsNoBitwarden collection ids, not folder ids.
organizationIdNoBitwarden organization id; used for org-scoped collection operations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changedv0.2.19
    • addedInput schema / properties / collectionIds / description
      Added value: +"Bitwarden collection ids, not folder ids."
    • addedInput schema / properties / favorite / description
      Added value: +"Mark the item as a favorite when true."
    • addedInput schema / properties / fields / description
      Added value: +"Custom fields to store on the item. Hidden fields are redacted in summaries."
    • addedInput schema / properties / fields / items / description
      Added value: +"Custom field stored on the item."
    • addedInput schema / properties / fields / items / properties / hidden / description
      Added value: +"Hide the field value in summaries when true."
    • addedInput schema / properties / fields / items / properties / name / description
      Added value: +"Custom field name stored on the item."
    • addedInput schema / properties / fields / items / properties / value / description
      Added value: +"Custom field value stored on the item."
    • addedInput schema / properties / folderId / description
      Added value: +"Personal folder id, not an organization collection id."
    • addedInput schema / properties / identity / description
      Added value: +"Structured identity profile data to store on the item."
    • addedInput schema / properties / identity / properties / address1 / description
      Added value: +"Primary street address line."
    • addedInput schema / properties / identity / properties / address2 / description
      Added value: +"Secondary street address line."
    • addedInput schema / properties / identity / properties / address3 / description
      Added value: +"Tertiary street address line."
    • addedInput schema / properties / identity / properties / city / description
      Added value: +"City for the identity."
    • addedInput schema / properties / identity / properties / company / description
      Added value: +"Company or organization name."
    • addedInput schema / properties / identity / properties / country / description
      Added value: +"Country for the identity."
    • addedInput schema / properties / identity / properties / email / description
      Added value: +"Email address for the identity."
    • addedInput schema / properties / identity / properties / firstName / description
      Added value: +"Given name for the identity."
    • addedInput schema / properties / identity / properties / lastName / description
      Added value: +"Family name for the identity."
    • addedInput schema / properties / identity / properties / licenseNumber / description
      Added value: +"Driver license or similar id number for the identity."
    • addedInput schema / properties / identity / properties / middleName / description
      Added value: +"Middle name for the identity."
    • addedInput schema / properties / identity / properties / passportNumber / description
      Added value: +"Passport number associated with the identity."
    • addedInput schema / properties / identity / properties / phone / description
      Added value: +"Phone number for the identity."
    • addedInput schema / properties / identity / properties / postalCode / description
      Added value: +"Postal or ZIP code for the identity."
    • addedInput schema / properties / identity / properties / ssn / description
      Added value: +"Social security number or equivalent national id."
    • addedInput schema / properties / identity / properties / state / description
      Added value: +"State, province, or region for the identity."
    • addedInput schema / properties / identity / properties / title / description
      Added value: +"Honorific or title for the identity."
    • addedInput schema / properties / identity / properties / username / description
      Added value: +"Username associated with the identity."
    • addedInput schema / properties / name / description
      Added value: +"Display name for the identity item."
    • addedInput schema / properties / notes / description
      Added value: +"Optional note text stored on the item."
    • addedInput schema / properties / organizationId / description
      Added value: +"Bitwarden organization id; used for org-scoped collection operations."
  2. Addedv0.1.20

TDQS

A4.2/5.0
Behavior4/5

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

Description adds context beyond annotations: summaries redact sensitive fields and hidden custom fields. Annotations only say not read-only and not destructive, so this is useful.

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?

Two sentences, no redundancy. First sentence states purpose, second adds behavioral detail. Highly efficient.

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

Completeness4/5

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

No output schema, but description notes redaction behavior. Covers key aspects given complexity, though could detail return format more. Schema fills in parameter details.

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?

Schema coverage is 100% with detailed descriptions, so baseline is 3. Description mentions 'structured identity fields plus custom fields and scoping' but adds little extra meaning beyond the schema.

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

Purpose5/5

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

Clearly states 'Create an identity item' with verb and resource. Distinguishes from siblings by specifying 'instead of a login or card.'

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

Usage Guidelines4/5

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

Explicitly says to use for personal/contact/address data and not for login or card. Provides alternative tool types but lacks when-not-to-use or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools