Skip to main content
Glama
ricleedo

Google Services MCP Server

by ricleedo

calendar-get-event

Retrieve specific calendar events by ID to access event details, manage schedules, and coordinate activities using Google Calendar data.

Instructions

Get a specific calendar event by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID
calendarIdNoCalendar ID - Available options: 'primary' (Primary Calendar)primary

Implementation Reference

  • The main handler function that retrieves a specific calendar event using Google Calendar API's events.get method, extracts relevant details, and formats the response as Markdown using formatEventToMarkdown.
    export async function getEvent(
      params: z.infer<ReturnType<typeof getEventSchema>>
    ) {
      try {
        const auth = createCalendarAuth();
        const calendar = google.calendar({ version: "v3", auth });
    
        const response = await calendar.events.get({
          calendarId: params.calendarId,
          eventId: params.eventId,
        });
    
        const event = response.data;
        const eventDetail = {
          id: event.id,
          summary: event.summary,
          description: event.description,
          location: event.location,
          start: event.start,
          end: event.end,
          attendees: event.attendees?.map((a) => ({
            email: a.email,
            displayName: a.displayName,
            responseStatus: a.responseStatus,
          })),
          creator: event.creator,
          organizer: event.organizer,
          htmlLink: event.htmlLink,
          status: event.status,
          created: event.created,
          updated: event.updated,
          recurrence: event.recurrence,
        };
    
        return {
          content: [
            {
              type: "text" as const,
              text: formatEventToMarkdown(eventDetail),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error getting event: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining input parameters for the calendar-get-event tool: eventId (required) and calendarId (optional, defaults to 'primary').
    export const getEventSchema = () =>
      z.object({
        eventId: z.string().describe("Event ID"),
        calendarId: z
          .string()
          .default("primary")
          .describe(getCalendarDescription()),
      });
  • src/index.ts:233-240 (registration)
    Registers the 'calendar-get-event' tool with the MCP server inside registerCalendarTools function, providing name, description, input schema from getEventSchema, and handler that delegates to getEvent.
    server.tool(
      "calendar-get-event",
      "Get a specific calendar event by ID",
      getEventSchema().shape,
      async (params) => {
        return await getEvent(params);
      }
    );
  • Helper function used by getEvent to format the retrieved event data into a readable Markdown string for the tool response.
    function formatEventToMarkdown(event: any): string {
      let markdown = `# ${event.summary || 'Untitled Event'}\n\n`;
      
      if (event.description) markdown += `${event.description}\n\n`;
      
      const startDate = event.start?.dateTime ? new Date(event.start.dateTime) : null;
      const endDate = event.end?.dateTime ? new Date(event.end.dateTime) : null;
      
      if (startDate) {
        markdown += `Start: ${startDate.toLocaleString()}  \n`;
      }
      if (endDate) {
        markdown += `End: ${endDate.toLocaleString()}  \n`;
      }
      
      if (event.location) markdown += `Location: ${event.location}  \n`;
      
      if (event.attendees && event.attendees.length > 0) {
        markdown += `Attendees: ${event.attendees.map((a: any) => {
          let attendee = a.email || a;
          if (a.responseStatus) {
            const status = a.responseStatus === 'accepted' ? '✅' : 
                         a.responseStatus === 'declined' ? '❌' : 
                         a.responseStatus === 'tentative' ? '❓' : '⏳';
            attendee += ` ${status}`;
          }
          return attendee;
        }).join(', ')}  \n`;
      }
      
      if (event.htmlLink) markdown += `Calendar Link: [View Event](${event.htmlLink})  \n`;
      if (event.id) markdown += `Event ID: \`${event.id}\`  \n`;
      
      return markdown;
    }
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 burden of behavioral disclosure. It states the tool retrieves an event but doesn't mention whether this is a read-only operation, if it requires specific permissions, what happens if the event doesn't exist, or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 front-loads the core purpose ('Get a specific calendar event by ID') with zero wasted words. It's appropriately sized for a simple retrieval tool, making it easy to parse and understand quickly.

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?

Given the tool's low complexity (2 parameters, no output schema) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it fails to address behavioral aspects like error handling or return format. For a retrieval tool, more context on what 'Get' entails (e.g., data returned, permissions) would improve completeness.

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 both parameters ('eventId' and 'calendarId') fully documented in the schema. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage examples. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('Get') and resource ('a specific calendar event by ID'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'calendar-list-events' (which lists multiple events) by specifying retrieval of a single event. However, it doesn't explicitly mention the calendar resource itself, which could be slightly more specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you need a specific event identified by ID, which differentiates it from 'calendar-list-events' for listing multiple events. However, it lacks explicit guidance on when to use this versus alternatives like 'calendar-update-event' or prerequisites such as needing an existing event ID. No exclusions or detailed context are provided.

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/ricleedo/Google-Service-MCP'

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