Skip to main content
Glama
mumunha

Cal.com Calendar MCP Server

by mumunha

calcom_delete_appointment

Cancel appointments in Cal.com by deleting them using the booking ID. This tool removes scheduled events from your calendar.

Instructions

Deletes an existing appointment from Cal.com calendar. Use this for canceling appointments. Requires booking ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookingIdYesThe Cal.com booking ID to delete
reasonNoOptional reason for cancellation

Implementation Reference

  • Core handler function that executes the deletion logic by calling the Cal.com API DELETE /bookings/{bookingId} endpoint, handles rate limiting, errors, and formats the response.
    async function deleteAppointment(bookingId: number, reason?: string) {
      checkRateLimit();
      
      try {
        await calComApiClient.delete(`/bookings/${bookingId}`, {
          data: reason ? { reason } : undefined
        });
        
        return `Appointment deleted successfully! Booking ID: ${bookingId}
    ${reason ? `Reason: ${reason}` : ""}`;
      } catch (error: any) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Failed to delete appointment: ${error.response?.data?.message || error.message}`);
        }
        throw new Error(`Failed to delete appointment: ${String(error)}`);
      }
    }
  • Tool call dispatcher in CallToolRequestSchema handler that validates arguments and invokes the deleteAppointment function.
    case "calcom_delete_appointment": {
      if (!isCalComDeleteAppointmentArgs(args)) {
        throw new Error("Invalid arguments for calcom_delete_appointment");
      }
      const { bookingId, reason } = args;
      const result = await deleteAppointment(bookingId, reason);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
  • Type guard function for validating input arguments to the calcom_delete_appointment tool.
    function isCalComDeleteAppointmentArgs(args: unknown): args is { 
      bookingId: number; 
      reason?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "bookingId" in args
      );
    }
  • index.ts:80-100 (registration)
    Tool definition object including name, description, and input schema, used for registration.
    const DELETE_APPOINTMENT_TOOL: Tool = {
      name: "calcom_delete_appointment",
      description:
        "Deletes an existing appointment from Cal.com calendar. " +
        "Use this for canceling appointments. " +
        "Requires booking ID. ",
      inputSchema: {
        type: "object",
        properties: {
          bookingId: {
            type: "number",
            description: "The Cal.com booking ID to delete"
          },
          reason: {
            type: "string",
            description: "Optional reason for cancellation"
          }
        },
        required: ["bookingId"],
      }
    };
  • index.ts:379-386 (registration)
    Registration of all tools including calcom_delete_appointment in the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        ADD_APPOINTMENT_TOOL, 
        UPDATE_APPOINTMENT_TOOL, 
        DELETE_APPOINTMENT_TOOL, 
        LIST_APPOINTMENTS_TOOL
      ],
    }));
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 deletes appointments and requires a booking ID, but does not disclose critical behavioral traits such as permissions needed, whether deletions are reversible, rate limits, or what happens to associated data (e.g., notifications). For a destructive mutation tool with zero annotation coverage, this is a significant gap.

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 appropriately sized and front-loaded, with two concise sentences that directly address the tool's purpose and key requirement. Every sentence earns its place, with no wasted words or redundancy.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects (e.g., permissions, reversibility), does not explain return values or errors, and does not fully address the tool's complexity in a calendar management context. The description should do more to compensate for the missing structured data.

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 already documents both parameters (bookingId and reason) fully. The description adds minimal value beyond the schema by mentioning 'Requires booking ID' and implying the reason is for cancellation, but does not provide additional syntax, format, or usage details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Deletes') and resource ('an existing appointment from Cal.com calendar'), and distinguishes it from siblings by focusing on deletion/cancellation rather than creation, listing, or updating. The phrase 'for canceling appointments' reinforces the purpose.

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 canceling appointments'), but does not explicitly mention when not to use it or name alternatives (e.g., using calcom_update_appointment for modifications instead). It implies usage by stating the purpose, but lacks explicit exclusions or sibling comparisons.

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