Skip to main content
Glama

Create contact

nextcloud_create_contact
Idempotent

Create a new contact in a Nextcloud address book by providing the address book URL and full name, with optional emails, phones, title, organization, and notes.

Instructions

Create one contact in an address book.

PUT /remote.php/dav/addressbooks/users/{user}/{book}/{uid}.vcf

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address_book_url": "<address_book_url>",
      "full_name": "<full_name>"
    },
    "name": "nextcloud_create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
titleNo
emailsNo
phonesNo
full_nameYes
organizationNo
address_book_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.0.0
    • addedInput schema / properties / emails
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • removedInput schema / properties / filename
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null
      -}
    • addedInput schema / properties / full_name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / note
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / organization
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / phones
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • removedInput schema / properties / vcard_data
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "address_book_url",
      -  "vcard_data"
      -]New value: +[
      +  "address_book_url",
      +  "full_name"
      +]
  2. First observedv2.3.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered without the description. The description adds the raw DAV endpoint, which hints at the underlying protocol but says nothing about duplicate handling, required permissions, error behavior, or whether an existing contact at the same UID is overwritten.

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?

Two compact lines with the purpose front-loaded ahead of the technical endpoint. Nothing is redundant, though the endpoint line consumes space that could have documented parameters.

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?

For a 7-parameter write tool with zero schema descriptions and no output schema, the description is far too thin. It neither documents the optional fields nor explains how to discover a valid address_book_url, leaving the agent under-equipped to invoke it correctly.

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% across 7 parameters, so the description carries the full burden and largely fails. The path template vaguely maps {book} to address_book_url, but the five optional fields (note, title, emails, phones, organization) and the format of full_name or the address book URL are never explained.

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?

"Create one contact in an address book" gives a specific verb and resource, and the PUT path makes the target unambiguous. It stops short of contrasting with nextcloud_update_contact or nextcloud_get_contact, so the agent must infer that this only creates new records.

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 on when to use this versus nextcloud_update_contact, nor any prerequisite such as obtaining address_book_url from nextcloud_list_address_books. The agent is left to infer the workflow entirely from sibling names.

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