Skip to main content
Glama
erickva

Google Calendar - No deletion

by erickva

create_event

Add new events to Google Calendar without the risk of deletion. Specify title, start/end times, location, description, and attendee emails.

Instructions

Create a new calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesNoList of attendee email addresses
descriptionNoEvent description
endYesEnd time in ISO format
locationNoEvent location
startYesStart time in ISO format
summaryYesEvent title

Implementation Reference

  • The main handler function that creates a new calendar event using Google Calendar API. It destructures arguments, builds the event object with timezone, inserts into primary calendar, and returns success or formatted error.
    private async handleCreateEvent(args: any) {
      try {
        const { summary, location, description, start, end, attendees = [] } = args;
    
        const event = {
          summary,
          location,
          description,
          start: {
            dateTime: start,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          },
          end: {
            dateTime: end,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          },
          attendees: attendees.map((email: string) => ({ email })),
        };
    
        const response = await this.calendar.events.insert({
          calendarId: 'primary',
          requestBody: event,
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Event created successfully. Event ID: ${response.data.id}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Error creating event: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
  • Input schema for the create_event tool, specifying required fields (summary, start, end) and optional fields (location, description, attendees).
    inputSchema: {
      type: 'object',
      properties: {
        summary: {
          type: 'string',
          description: 'Event title',
        },
        location: {
          type: 'string',
          description: 'Event location',
        },
        description: {
          type: 'string',
          description: 'Event description',
        },
        start: {
          type: 'string',
          description: 'Start time in ISO format',
        },
        end: {
          type: 'string',
          description: 'End time in ISO format',
        },
        attendees: {
          type: 'array',
          items: { type: 'string' },
          description: 'List of attendee email addresses',
        },
      },
      required: ['summary', 'start', 'end']
    },
  • src/index.ts:173-207 (registration)
    Registers the create_event tool in the ListToolsRequestSchema handler, providing name, description, and input schema.
    {
      name: 'create_event',
      description: 'Create a new calendar event',
      inputSchema: {
        type: 'object',
        properties: {
          summary: {
            type: 'string',
            description: 'Event title',
          },
          location: {
            type: 'string',
            description: 'Event location',
          },
          description: {
            type: 'string',
            description: 'Event description',
          },
          start: {
            type: 'string',
            description: 'Start time in ISO format',
          },
          end: {
            type: 'string',
            description: 'End time in ISO format',
          },
          attendees: {
            type: 'array',
            items: { type: 'string' },
            description: 'List of attendee email addresses',
          },
        },
        required: ['summary', 'start', 'end']
      },
    },
  • src/index.ts:240-241 (registration)
    In the CallToolRequestSchema handler, routes 'create_event' tool calls to the handleCreateEvent method.
    case 'create_event':
      return await this.handleCreateEvent(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention permissions required, whether it sends invitations to attendees, error conditions, or what happens on success/failure. This leaves significant gaps 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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a straightforward creation tool and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns event ID, sends notifications), error handling, or behavioral nuances. The 100% schema coverage helps with parameters but doesn't compensate for the lack of operational context.

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?

The schema description coverage is 100%, with all parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured fields, so it meets the baseline for high schema coverage.

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?

The description clearly states the action ('Create') and resource ('calendar event'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'modify_email' or 'meeting_suggestion' that might also involve calendar operations, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. Given sibling tools like 'list_events' and 'meeting_suggestion', there's no indication of whether this is for manual creation versus automated suggestions, or any prerequisites for use.

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

Related 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/erickva/google-workspace-mcp-server-no-calendar-deletetion'

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