Skip to main content
Glama
mumunha

Cal.com Calendar MCP Server

by mumunha

calcom_add_appointment

Schedule new meetings or appointments in Cal.com calendar by providing event type, time slots, and attendee details.

Instructions

Creates a new appointment in Cal.com calendar. Use this for scheduling new meetings or appointments. Requires event type ID, start time, end time, name, email, and optional notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventTypeIdYesThe Cal.com event type ID
startTimeYesStart time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)
endTimeYesEnd time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)
nameYesAttendee's name
emailYesAttendee's email
notesNoOptional notes for the appointment

Implementation Reference

  • Core handler function that executes the calcom_add_appointment tool logic: performs rate limiting, makes POST request to Cal.com API to create booking, and returns success message.
    async function addAppointment(
      eventTypeId: number, 
      startTime: string, 
      endTime: string, 
      name: string, 
      email: string, 
      notes?: string
    ) {
      checkRateLimit();
      
      try {
        const response = await calComApiClient.post('/bookings', {
          eventTypeId,
          start: new Date(startTime).toISOString(),
          end: new Date(endTime).toISOString(),
          name,
          email,
          notes,
        });
        
        const booking = response.data;
        
        return `Appointment created successfully! Booking ID: ${booking.id}
    Event Type: ${booking.eventTypeId}
    Start Time: ${booking.startTime}
    End Time: ${booking.endTime}
    Attendee: ${name} (${email})
    ${notes ? `Notes: ${notes}` : ""}`;
      } catch (error: any) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Failed to create appointment: ${error.response?.data?.message || error.message}`);
        }
        throw new Error(`Failed to create appointment: ${String(error)}`);
      }
    }
  • Tool definition including name, description, and input schema for calcom_add_appointment.
    const ADD_APPOINTMENT_TOOL: Tool = {
      name: "calcom_add_appointment",
      description:
        "Creates a new appointment in Cal.com calendar. " +
        "Use this for scheduling new meetings or appointments. " +
        "Requires event type ID, start time, end time, name, email, and optional notes. ",
      inputSchema: {
        type: "object",
        properties: {
          eventTypeId: {
            type: "number",
            description: "The Cal.com event type ID"
          },
          startTime: {
            type: "string",
            description: "Start time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)"
          },
          endTime: {
            type: "string",
            description: "End time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)"
          },
          name: {
            type: "string",
            description: "Attendee's name"
          },
          email: {
            type: "string",
            description: "Attendee's email"
          },
          notes: {
            type: "string",
            description: "Optional notes for the appointment",
          }
        },
        required: ["eventTypeId", "startTime", "endTime", "name", "email"],
      },
    };
  • index.ts:379-386 (registration)
    Registers the calcom_add_appointment tool (via ADD_APPOINTMENT_TOOL) in the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        ADD_APPOINTMENT_TOOL, 
        UPDATE_APPOINTMENT_TOOL, 
        DELETE_APPOINTMENT_TOOL, 
        LIST_APPOINTMENTS_TOOL
      ],
    }));
  • Tool dispatch handler in CallToolRequestSchema that validates arguments and calls the addAppointment function.
    case "calcom_add_appointment": {
      if (!isCalComAddAppointmentArgs(args)) {
        throw new Error("Invalid arguments for calcom_add_appointment");
      }
      const { eventTypeId, startTime, endTime, name, email, notes } = args;
      const result = await addAppointment(eventTypeId, startTime, endTime, name, email, notes);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
  • Type guard function for validating input arguments to calcom_add_appointment.
    function isCalComAddAppointmentArgs(args: unknown): args is { 
      eventTypeId: number; 
      startTime: string; 
      endTime: string; 
      name: string; 
      email: string; 
      notes?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "eventTypeId" in args &&
        "startTime" in args &&
        "endTime" in args &&
        "name" in args &&
        "email" in args
      );
    }
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. While it mentions the tool creates appointments and lists required parameters, it doesn't disclose important behavioral traits like authentication requirements, error handling, rate limits, or what happens on success (e.g., returns appointment ID). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with two sentences that efficiently convey purpose and parameters. It's front-loaded with the main action and could be slightly more structured but contains no wasted words.

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 incomplete. It doesn't explain what happens after creation (success response, error cases), authentication requirements, or system constraints. Given the complexity of creating calendar appointments, more contextual information is needed.

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%, providing complete parameter documentation. The description adds minimal value beyond the schema by listing the parameters but doesn't provide additional context about their meaning, relationships, or usage patterns. This 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.

Purpose5/5

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

The description clearly states the specific action ('Creates a new appointment'), resource ('in Cal.com calendar'), and purpose ('for scheduling new meetings or appointments'). It distinguishes from sibling tools like delete, list, and update by focusing exclusively on creation.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('for scheduling new meetings or appointments'), but does not explicitly mention when not to use it or name alternatives like the sibling tools. This gives good guidance but lacks explicit 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/mumunha/cal_dot_com_mcpserver'

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