Skip to main content
Glama

create_event

Add a new calendar event with title, start and end times, description, location, recurrence, attendees, and reminders.

Instructions

Create a new calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEvent end time (ISO format)
startYesEvent start time (ISO format)
accountNoAccount alias
all_dayNoWhether this is an all-day event
summaryYesEvent title/summary
locationNoEvent location
related_toNoList of related component UIDs
descriptionNoEvent description
calendar_uidYesCalendar UID
alarm_minutesNoReminder minutes before event as string ('-10080' to '10080')
attendees_jsonNoJSON string of attendees list [{email, name, role, status, rsvp}]
recurrence_ruleNoRRULE for recurring events (e.g., 'FREQ=WEEKLY;BYDAY=MO')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden but only states 'Create a new calendar event'. It does not disclose behavioral traits such as success/failure behavior, required permissions, or side effects. This is insufficient for a mutation tool.

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?

Single sentence with no fluff, perfectly concise.

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

Completeness2/5

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

Despite having an output schema, the tool has 12 parameters and the description is extremely minimal. It lacks context about prerequisites, default behavior, or usage constraints, making it incomplete for a complex tool.

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 100%, so baseline is 3. The description adds no parameter meaning beyond the schema, thus no improvement.

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 'Create a new calendar event' clearly states the action (create) and the resource (calendar event). It distinguishes from siblings like bulk_create_events and create_recurring_event, making it specific.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that for recurring events, 'create_recurring_event' should be used instead, leaving the agent without decision-making information.

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/democratize-technology/chronos-mcp'

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