Skip to main content
Glama

create_event

Schedule bookings, appointments, or meetings on a calendar. Use hold status to tentatively reserve slots that auto-release after a set time.

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.
Behavior5/5

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

The annotations (readOnlyHint=false, destructiveHint=false) indicate a mutation that is not destructive. The description adds valuable behavioral details: blocking availability, appearing in queries, and the hold auto-release mechanism. No contradictions.

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 concise with two sentences that front-load the main purpose and then provide key usage details. Every sentence adds value without redundancy.

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 complexity of 10 parameters and no output schema, the description covers essential behavioral aspects (availability blocking, hold mechanics, reminder behavior) and prerequisite (calendar_id source). It is complete enough for an AI agent.

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 coverage is 100%, but the description adds meaning beyond schema: it explains the effect of status='hold', the purpose of hold_expires_at, and the reminder behavior (webhook and iCal alarm). It also tells where to get calendar_id.

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 'Create a booking, appointment, meeting, hold, or any scheduled event on a calendar.' The verb is specific and the resource is well-defined. It distinguishes from siblings like update_event and confirm_event by focusing on creation.

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 provides clear context: the event blocks availability, and the calendar_id source is given. It explains when to use status='hold' with hold_expires_at for tentative reservations. However, it does not explicitly mention when not to use the tool or contrast with alternatives like create_proposal.

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