Skip to main content
Glama

create_event

Create bookings, appointments, meetings, or holds on a calendar. Block agent availability and auto-release tentative holds with expiration.

Instructions

Create a booking, appointment, meeting, hold, or any scheduled event on a calendar. The calendar_id comes from create_calendar or list_events. Once created, this event blocks the agent's availability during that time and appears in availability queries. Use status="hold" with hold_expires_at to tentatively reserve a slot that auto-releases on TTL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesEvent title
statusNoEvent status. "hold" creates a tentative reservation that auto-expires at hold_expires_at. Defaults to "confirmed".
all_dayNoWhether this is an all-day event
end_timeYesEnd time (ISO 8601)
remindersNoReminder offsets in minutes before start_time (e.g. [10, 1440]). Each fires an event.reminder webhook and shows as an alarm in the iCal feed. Omit or null to inherit the calendar default (then the system default of 10 min); [] for no reminders.
start_timeYesStart time (ISO 8601)
calendar_idYesCalendar ID to add the event to
descriptionNoOptional event description
hold_priorityNoOnly valid with status="hold". Higher-priority overlapping holds pre-empt lower-priority ones. Defaults to 0.
hold_expires_atNoRequired when status="hold". ISO 8601 timestamp 30s-15min in the future. Auto-releases the hold when reached.
recurrence_ruleNoMake this a recurring series (RFC 5545 RRULE subset, no "RRULE:" prefix), e.g. "FREQ=WEEKLY;BYDAY=MO,WE;COUNT=12". Supports FREQ=DAILY/WEEKLY/MONTHLY/YEARLY, INTERVAL, COUNT (max 730) or UNTIL, BYDAY (weekly list or monthly ordinal like 2TU/-1FR), BYMONTHDAY (1-28 or -1). start_time must match the rule pattern; expansion is UTC-only. Not allowed with status="hold". Free plan: max 5 recurring events, series must end within 90 days.
Behavior4/5

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

Annotations indicate this is a mutation (readOnlyHint=false). The description adds that events block agent availability and appear in availability queries, and explains hold auto-release. No contradiction. Could mention webhook or notification side effects, but not required.

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 is two sentences plus a hold-specific note. It is concise, front-loaded with the main purpose, and presents key information efficiently without redundancy.

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?

The tool has 11 parameters and special behavior (hold, recurrence). The description covers availability impact and hold specifics but does not mention return values (e.g., created event ID). No output schema exists, so this is a notable gap. Otherwise adequate.

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 descriptions for all 11 parameters. The description adds context about calendar_id source and hold behavior, but does not significantly expand on parameter semantics beyond what's in the schema. Baseline 3 is appropriate.

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 clearly states the tool creates events (bookings, appointments, meetings, holds) on a calendar. It distinguishes from siblings like create_calendar (creates calendars) and create_proposal, and mentions specific use cases like holds.

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 description explains when to use this tool (to create scheduled events) and where calendar_id comes from. It provides guidance on using status="hold" for tentative reservations. It does not explicitly list alternatives or when not to use, but the sibling context suffices.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Chronary/chronary-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server