Skip to main content
Glama

Create event

nextcloud_create_event
Idempotent

Create a calendar event with times, attendees, location, and description. Control whether attendees receive invitations or remain drafts.

Instructions

Create one event. Attendees get a draft invitation unless send_invitations.

PUT /remote.php/dav/calendars/{user}/{calendar}/{uid}.ics

start/end are ISO 8601 (a naive time is UTC); end defaults to one hour (one day when all_day) after start. With send_invitations false the attendees are marked SCHEDULE-AGENT=CLIENT, so the server sends no invitation email.

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": {
      "calendar_url": "<calendar_url>",
      "summary": "<summary>",
      "start": "<start>"
    },
    "name": "nextcloud_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startYes
all_dayNo
summaryYes
locationNo
attendeesNo
descriptionNo
calendar_urlYes
send_invitationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv3.0.0
    • addedInput schema / properties / all_day
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / attendees
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / end
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • removedInput schema / properties / event_data
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / filename
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null
      -}
    • addedInput schema / properties / location
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / send_invitations
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / start
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / summary
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "calendar_url",
      -  "event_data"
      -]New value: +[
      +  "calendar_url",
      +  "summary",
      +  "start"
      +]
  2. First observedv2.3.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world operation, and the description adds genuine context on top: attendees receive a draft invitation unless send_invitations is set, otherwise SCHEDULE-AGENT=CLIENT suppresses server-side email. The endpoint path also explains why the operation is idempotent (writes to a specific {uid}.ics).

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?

Short and front-loaded: the core action comes first, then invocation details, then invitation semantics. The raw PUT path and reST-style double backticks are slightly noisy but the path carries real information about the target resource.

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

Completeness3/5

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

For a 9-parameter mutation with no output schema, the description covers the trickiest semantics (time formats, defaults, invitation side effects) that annotations cannot express. It does not say what the call returns (uid, href, created object) or what shape calendar_url takes, which are real gaps for an agent building a valid call.

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 description coverage is 0% across 9 parameters, so the description must compensate. It usefully defines start/end formats (ISO 8601, naive = UTC) and the end default (+1 hour, +1 day with all_day), plus send_invitations and attendees semantics, but leaves calendar_url (URL vs. calendar ID), summary, location, and description entirely undefined.

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?

Opens with a specific verb+resource ('Create one event') and the PUT path to a calendar .ics resource confirms it targets calendar events rather than contacts, cards, or notes. It is not explicitly contrasted with nextcloud_update_event or nextcloud_list_events, but the verb alone separates it from those siblings.

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?

There is no when-to-use guidance, no statement about when to prefer update_event over create_event, and no prerequisite noted for calendar_url (an agent must infer it needs an existing calendar from list_calendars). Only the send_invitations behavior is explained, which is behavior rather than usage routing.

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