Skip to main content
Glama
mumunha

Cal.com Calendar MCP Server

by mumunha

calcom_update_appointment

Modify existing Cal.com appointments by rescheduling times or updating notes using the booking ID.

Instructions

Updates an existing appointment in Cal.com calendar. Use this for rescheduling or modifying existing appointments. Requires booking ID and the fields to update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookingIdYesThe Cal.com booking ID to update
startTimeNoNew start time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)
endTimeNoNew end time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)
notesNoNew notes for the appointment

Implementation Reference

  • The main handler function that executes the tool logic: validates optional fields, constructs update data, calls Cal.com API PATCH /bookings/{bookingId}, and returns success message or throws error.
    async function updateAppointment(
      bookingId: number, 
      startTime?: string, 
      endTime?: string, 
      notes?: string
    ) {
      checkRateLimit();
      
      try {
        const updateData: Record<string, any> = {};
        
        if (startTime) updateData.start = new Date(startTime).toISOString();
        if (endTime) updateData.end = new Date(endTime).toISOString();
        if (notes !== undefined) updateData.notes = notes;
        
        const response = await calComApiClient.patch(`/bookings/${bookingId}`, updateData);
        
        const booking = response.data;
        
        return `Appointment updated successfully! Booking ID: ${booking.id}
    ${startTime ? `New Start Time: ${booking.startTime}` : ""}
    ${endTime ? `New End Time: ${booking.endTime}` : ""}
    ${notes !== undefined ? `New Notes: ${notes}` : ""}`;
      } catch (error: any) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Failed to update appointment: ${error.response?.data?.message || error.message}`);
        }
        throw new Error(`Failed to update appointment: ${String(error)}`);
      }
    }
  • Type guard function for input schema validation of calcom_update_appointment arguments.
    function isCalComUpdateAppointmentArgs(args: unknown): args is { 
      bookingId: number; 
      startTime?: string; 
      endTime?: string; 
      notes?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "bookingId" in args
      );
    }
  • index.ts:50-78 (registration)
    Tool registration object defining name, description, and JSON inputSchema for calcom_update_appointment.
    const UPDATE_APPOINTMENT_TOOL: Tool = {
      name: "calcom_update_appointment",
      description:
        "Updates an existing appointment in Cal.com calendar. " +
        "Use this for rescheduling or modifying existing appointments. " +
        "Requires booking ID and the fields to update. ",
      inputSchema: {
        type: "object",
        properties: {
          bookingId: {
            type: "number",
            description: "The Cal.com booking ID to update"
          },
          startTime: {
            type: "string",
            description: "New start time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)"
          },
          endTime: {
            type: "string",
            description: "New end time in ISO format (YYYY-MM-DDTHH:mm:ss.sssZ)"
          },
          notes: {
            type: "string",
            description: "New notes for the appointment"
          }
        },
        required: ["bookingId"],
      }
    };
  • Dispatcher handler case within CallToolRequestSchema that performs arg validation and delegates to the updateAppointment function.
    case "calcom_update_appointment": {
      if (!isCalComUpdateAppointmentArgs(args)) {
        throw new Error("Invalid arguments for calcom_update_appointment");
      }
      const { bookingId, startTime, endTime, notes } = args;
      const result = await updateAppointment(bookingId, startTime, endTime, notes);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
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 mentions 'Requires booking ID and the fields to update,' which hints at prerequisites but doesn't cover critical aspects like authentication needs, rate limits, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's 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.

Conciseness4/5

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

The description is concise and front-loaded, with two sentences that efficiently convey purpose and usage. Every sentence adds value: the first states what the tool does, and the second provides context and prerequisites. There's no redundant or wasted information, making it easy to parse quickly.

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?

Given the tool's complexity (a mutation operation with 4 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral details like whether updates are partial or full. For a tool that modifies data, more context is needed to ensure safe and correct usage by an AI agent.

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%, so the schema fully documents all parameters (bookingId, startTime, endTime, notes). The description adds minimal value beyond the schema by mentioning 'Requires booking ID and the fields to update,' which reinforces the required parameter but doesn't provide additional syntax or format details. Baseline 3 is appropriate when the schema handles most of the parameter documentation.

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 tool's purpose: 'Updates an existing appointment in Cal.com calendar.' It specifies the verb ('Updates') and resource ('appointment in Cal.com calendar'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'calcom_add_appointment' or 'calcom_delete_appointment' beyond mentioning 'existing appointment,' which is implied but not directly contrasted.

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 usage context: 'Use this for rescheduling or modifying existing appointments.' This gives practical scenarios (rescheduling, modifying) and implies it's for updates rather than creation or deletion. It doesn't explicitly state when not to use it or name alternatives like 'calcom_add_appointment' for new appointments, but the context is sufficient for basic guidance.

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