Skip to main content
Glama
tumf

fastmcp-gsuite

by tumf

create_calendar_event

Add an event to any Google Calendar by specifying title, start and end time, and optional details such as location, attendees, and reminders.

Instructions

Create a new event in a specified calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe EMAIL of the Google account. Choose from:
calendar_idYesThe ID of the calendar to add the event to (use 'primary' for the primary calendar).
summaryYesThe title or summary of the event.
start_datetimeYesStart date/time in ISO 8601 format (e.g., '2024-04-15T10:00:00Z' or '2024-04-15' for all-day).
end_datetimeYesEnd date/time in ISO 8601 format (e.g., '2024-04-15T11:00:00Z' or '2024-04-16' for all-day).
descriptionNoOptional description or details for the event.
locationNoOptional location for the event.
attendeesNoOptional list of attendee email addresses.
timezoneNoIANA timezone name (e.g., 'America/Los_Angeles'). Defaults to UTC if omitted.
transparencyNoEvent visibility: 'transparent' (show as free) or 'opaque' (show as busy).
remindersNoReminder config, e.g. {"useDefault": false, "overrides": []} to disable all reminders.
color_idNoGoogle Calendar color ID (1-11).
recurrenceNoList of RRULE strings, e.g. ["RRULE:FREQ=WEEKLY;BYDAY=MO"].
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. Only says 'create' but does not mention permissions, side effects, or success response. Lacks details on event creation behavior.

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?

One sentence, no unnecessary words or repetition. Front-loaded and efficient.

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?

Tool has many parameters and no output schema. Description is minimal and does not explain return values, confirmation, or constraints like timezone handling. Incomplete given complexity.

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%, so baseline is 3. Description does not add extra meaning beyond parameter names and schema descriptions.

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?

Description clearly states the action (create), resource (calendar event), and context (specified calendar). Distinguishes from sibling tools like update_calendar_event and delete_calendar_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 vs alternatives like update_calendar_event. Does not mention prerequisites or exclusions.

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/tumf/fastmcp-gsuite'

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