Skip to main content
Glama

create-calendar-event

Schedule meetings, all-day events, and recurring entries in a Dooray calendar by specifying times, attendees, location, alarms, and visibility.

Instructions

Create an event (일정 등록) in a Dooray calendar.

Required: calendarId, subject, startedAt, endedAt. Get calendarId from get-calendar-list (default=true is the user's own calendar).

Time Format:

  • Timed event: "2026-10-22T10:00:00+09:00"

  • Whole day event: set wholeDayFlag=true and use date format "2026-10-22+09:00". endedAt is the next day ("2026-10-23+09:00" for a one day event)

Attendees: {id, type} where type is "member" (organizationMemberId) or "email" (email address). Use get-my-member-info, get-project-member-list, get-member-list to find member IDs. Without attendees, the authenticated user is added as the attendee (the API rejects an event without one).

Examples:

  • Meeting: {"calendarId": "123", "subject": "주간 회의", "startedAt": "2026-10-22T10:00:00+09:00", "endedAt": "2026-10-22T11:00:00+09:00", "location": "4-5 회의실", "attendees": [{"id": "456", "type": "member"}]}

  • Whole day: {"calendarId": "123", "subject": "휴가", "startedAt": "2026-10-22+09:00", "endedAt": "2026-10-23+09:00", "wholeDayFlag": true}

  • Weekly: add "recurrenceRule": {"frequency": "weekly", "byday": "MO", "timezoneName": "Asia/Seoul"}

Returns: {id} of the created event.

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": {
      "calendarId": "<calendarId>",
      "subject": "<subject>",
      "startedAt": "<startedAt>",
      "endedAt": "<endedAt>"
    },
    "name": "create-calendar-event"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC (참조)
bodyNoEvent description
busyNotrue: busy (바쁨), false: free (한가함)
alarmsNoAlarms
endedAtYesEnd time (ISO 8601). Whole day: next day, e.g. 2026-10-23+09:00
subjectYesEvent title
locationNoLocation
attendeesNoAttendees (참석자). Use get-my-member-info, get-member-list to find member IDs
startedAtYesStart time (ISO 8601, e.g. 2026-10-22T10:00:00+09:00). Whole day: 2026-10-22+09:00
calendarIdYesCalendar ID to create the event in
visibilityNopublic (공개) or private (비공개)
wholeDayFlagNotrue for a whole day event
recurrenceRuleNoRecurrence rule for a recurring event

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses non-obvious runtime behavior: the API rejects events without an attendee, so the authenticated user is auto-added, whole-day events require the next day as endedAt, and the call returns {id}. These are exactly the failure modes an agent would otherwise hit blind.

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 definition is front-loaded with required parameters, then broken into clearly headed sections (Time Format, Attendees, Examples, Returns), so an agent can scan to the part it needs. It runs long, and the required-field list partly restates the schema's required array and per-field descriptions, which is the only real redundancy.

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?

For a 13-parameter mutation tool with nested objects and no output schema, it covers the return value, the tricky date conventions, attendee resolution, and recurrence. Remaining gaps are minor optional semantics (alarm triggers, visibility defaults) that the schema descriptions already spell out.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: the exact timestamp shape for timed vs. whole-day events, the {id, type} attendee contract, and a worked recurrenceRule example. Optional fields like alarms, visibility, and busy are left entirely to the schema, which is acceptable given its coverage.

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 opening line states a specific verb and resource ("Create an event in a Dooray calendar"), which clearly separates it from the update-calendar-event and delete-calendar-event siblings without requiring the agent to open another schema.

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?

It gives concrete routing guidance for prerequisites: use get-calendar-list and note the default=true semantics for the user's own calendar, and use get-my-member-info / get-project-member-list / get-member-list to obtain attendee IDs. What's missing is an explicit statement of when to prefer update-calendar-event instead, but the create-vs-modify boundary is largely implied by the verb.

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