Skip to main content
Glama
vcnngr

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_create

Create Google Calendar events with title, time, recurrence, attendees, and reminders; returns the new synced event for use in follow-up actions.

Instructions

Create an event (synced to Google Calendar). Returns the new event (see calendar.get).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd time; for all-day events the LAST day (inclusive). Default: start + duration.
colorNoEvent colour: lavender, sage, grape, flamingo, banana, tangerine, peacock, graphite, blueberry, basil, tomato (or 1-11, or #RRGGBB for the nearest).
rruleNoRecurrence rule (RFC 5545), e.g. FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10 or FREQ=DAILY;UNTIL=20261231T235959Z.
startYesStart: ISO 8601, 'YYYY-MM-DD HH:MM', 'DD/MM/YYYY HH:MM'; a date for all-day events.
titleYesEvent title.
all_dayNoAll-day event (start/end are dates).
confirmNoRequired (true) when attendees are given, because invitations are e-mailed.
calendarNoCalendar id or name (default: the account's primary calendar).
locationNoLocation text.
timezoneNoIANA zone for times without an offset (default Europe/Rome).Europe/Rome
attendeesNoGuest e-mail addresses. Google e-mails them an invitation: needs confirm=true.
remindersNoMinutes before start for pop-up reminders, e.g. [10, 60].
descriptionNoDescription / notes.
availabilityNobusy (default for timed events) / free (default for all-day) / tentative.
duration_minutesNoLength when end is omitted (default 60; for all-day, rounded up to days).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses only that the event syncs to Google Calendar and returns the new event. It omits that attendees trigger real e-mailed invitations requiring confirm=true, that recurrence/reminders have side effects, and whether the write is reversible.

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?

Two compact sentences with zero filler, and the core action is front-loaded ahead of the sync and return-value notes.

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?

For a 15-parameter mutation tool with no annotations and no output schema, the description is thin: the external side effect of e-mailed invitations, which is the riskiest behavior here, is left entirely to the schema property text. It does at least cover the sync behavior and redirect to calendar.get for the response shape.

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% across all 15 parameters, so defaults, formats, enum values, and the confirm requirement are already documented in the schema. The description adds no parameter-level meaning beyond referring to calendar.get for the return shape, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Create an event', plus a scope note that it is synced to Google Calendar. That distinguishes it from calendar_update and calendar_task_create, though it never explicitly names those siblings.

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 versus calendar_update (edit an existing event), calendar_add_meet (attach a Meet link), or calendar_task_create. The only pointer, 'see calendar.get', is about the return value, not about tool selection.

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

Deploy Server

Other Tools