Skip to main content
Glama

Create Event

create_event

Create a calendar event with title, start/end times, location, and notes. Optionally set as all-day or choose a target calendar.

Instructions

Create a new calendar event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesEvent title
startDateYesStart date/time (ISO 8601, e.g. '2026-03-15T09:00:00Z')
endDateYesEnd date/time (ISO 8601, e.g. '2026-03-15T10:00:00Z')
locationNoEvent location
descriptionNoEvent notes/description
calendarNoTarget calendar name. Defaults to first writable calendar.
allDayNoSet as all-day event
Behavior3/5

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

Annotations already indicate mutability (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds no extra behavioral context beyond what annotations provide.

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?

Single sentence is succinct and front-loaded, but could be slightly improved with additional context without being verbose.

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?

No output schema leads to uncertainty about return values. Missing details on defaults, error handling, or authentication expectations for a 7-parameter creation 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 covers all parameters with descriptions. The tool description does not add additional meaning beyond the schema, resulting in a baseline score of 3.

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 and resource, distinguishing it from siblings like update_event and create_recurring_event.

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 (e.g., create_recurring_event for recurring events, bulk_move_notes for bulk operations).

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/heznpc/AirMCP'

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