nc-mcp-server

create_event

Create a calendar event by providing calendar ID, title, and start time. Include optional end time, recurrence rule, or all-day flag for flexible scheduling.

Instructions

Create a new calendar event.

Args: calendar_id: Calendar identifier (e.g. "personal"). summary: Event title/summary. start: Start date or datetime in ISO 8601 format. For timed events: "2026-04-01T10:00:00Z" or "2026-04-01T10:00:00". For all-day events: "2026-04-01". end: End date or datetime. Optional — defaults to 1 hour after start for timed events, or next day for all-day events. all_day: Set to true for an all-day event. When true, start/end are dates only. description: Optional event description/notes. location: Optional event location. status: Event status: "CONFIRMED" (default), "TENTATIVE", or "CANCELLED". categories: Optional comma-separated category names (e.g. "Work,Meeting"). rrule: Optional recurrence rule in iCalendar RRULE format. Examples: "FREQ=DAILY;COUNT=5", "FREQ=WEEKLY;BYDAY=MO,WE,FR", "FREQ=MONTHLY;BYMONTHDAY=15;UNTIL=20261231T235959Z".

Returns: JSON object with the created event's uid and summary.

Input Schema

TableJSON Schema

Name	Required	Default
`end`	No
`rrule`	No
`start`	Yes
`status`	No	CONFIRMED
`all_day`	No
`summary`	Yes
`location`	No
`categories`	No
`calendar_id`	Yes
`description`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations are minimal (all false), so the description carries most of the behavioral burden. It goes beyond the schema by explaining default end time behavior, all-day date handling, status default, and RRULE examples. It does not explicitly warn about non-idempotency, but creation side effects are strongly implied by 'Create'.

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 uses a clean, front-loaded summary followed by a structured Args/Returns layout. Each parameter entry adds necessary detail without fluff, making the longer length justified by the tool's 10-parameter complexity.

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

Completeness5/5

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

Given the high parameter count and missing schema descriptions, the description covers every parameter, their defaults, and the return shape. An agent can invoke the tool correctly with only the information provided here, and the output schema makes the return details even clearer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates. Every parameter is explained with format expectations, defaults, and concrete examples (e.g., ISO 8601 formats, RRULE examples, all-day restrictions). This is far more useful than the bare input 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?

The description opens with a specific verb and resource: 'Create a new calendar event.' It clearly identifies the tool's function and is easily distinguished from siblings like get_event, update_event, and delete_event.

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?

The phrase 'Create a new calendar event' clearly establishes the intended use case of creating rather than reading, updating, or deleting an event. However, it does not explicitly name alternative tools or state when-not-to-use this tool, so it falls short of the highest bar.

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

Deploy Server