Skip to main content
Glama
mumunha

Cal.com Calendar MCP Server

by mumunha

calcom_list_appointments

Retrieve scheduled appointments from Cal.com calendar within a specified date range to view upcoming meetings and events.

Instructions

Lists appointments from Cal.com calendar. Can be filtered by date range. Returns a list of appointments with their details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format

Implementation Reference

  • Handler case in CallToolRequestSchema that validates arguments and invokes the listAppointments function to execute the tool logic.
    case "calcom_list_appointments": {
      if (!isCalComListAppointmentsArgs(args)) {
        throw new Error("Invalid arguments for calcom_list_appointments");
      }
      const { startDate, endDate } = args;
      const result = await listAppointments(startDate, endDate);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
  • Core helper function that performs the API call to Cal.com to fetch and format appointments within the given date range.
    async function listAppointments(startDate: string, endDate: string) {
      checkRateLimit();
      
      try {
        const response = await calComApiClient.get('/bookings', {
          params: {
            dateFrom: startDate,
            dateTo: endDate,
          }
        });
        
        const bookings = response.data;
        
        if (bookings.length === 0) {
          return "No appointments found for the selected date range.";
        }
        
        return bookings.map((booking: any) => `
    ID: ${booking.id}
    Event Type: ${booking.eventTypeId}
    Status: ${booking.status}
    Start Time: ${booking.startTime}
    End Time: ${booking.endTime}
    Attendees: ${booking.attendees.map((a: any) => `${a.name} (${a.email})`).join(", ")}
    ${booking.notes ? `Notes: ${booking.notes}` : ""}
    `).join("\n---\n");
      } catch (error: any) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Failed to list appointments: ${error.response?.data?.message || error.message}`);
        }
        throw new Error(`Failed to list appointments: ${String(error)}`);
      }
    }
  • Input argument validator (type guard) ensuring required startDate and endDate are present.
    function isCalComListAppointmentsArgs(args: unknown): args is { 
      startDate: string; 
      endDate: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "startDate" in args &&
        "endDate" in args
      );
    }
  • index.ts:379-386 (registration)
    Registers the calcom_list_appointments tool (via LIST_APPOINTMENTS_TOOL) in the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        ADD_APPOINTMENT_TOOL, 
        UPDATE_APPOINTMENT_TOOL, 
        DELETE_APPOINTMENT_TOOL, 
        LIST_APPOINTMENTS_TOOL
      ],
    }));
  • Tool definition including name, description, and input schema for validation.
    const LIST_APPOINTMENTS_TOOL: Tool = {
      name: "calcom_list_appointments",
      description:
        "Lists appointments from Cal.com calendar. " +
        "Can be filtered by date range. " +
        "Returns a list of appointments with their details. ",
      inputSchema: {
        type: "object",
        properties: {
          startDate: {
            type: "string",
            description: "Start date in YYYY-MM-DD format"
          },
          endDate: {
            type: "string",
            description: "End date in YYYY-MM-DD format"
          }
        },
        required: ["startDate", "endDate"],
      }
    };
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. It states the tool lists appointments and returns details, but doesn't disclose behavioral traits such as authentication requirements, rate limits, pagination, error handling, or what 'details' include. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with three sentences that are front-loaded: it states the purpose, filtering capability, and return value efficiently. However, the second sentence could be more integrated, and there's minor redundancy in mentioning 'lists' and 'returns', but overall it's well-structured with minimal waste.

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 complexity is low (a simple list operation with 2 parameters), schema coverage is high (100%), and no output schema is provided, the description is adequate but incomplete. It covers the basic purpose and filtering, but lacks details on return format, error cases, or behavioral context, making it minimally viable but with clear gaps for an agent to rely on.

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 input schema already documents both parameters (startDate and endDate) with their formats. The description adds that it 'can be filtered by date range', which aligns with the schema but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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: 'Lists appointments from Cal.com calendar' with the verb 'lists' and resource 'appointments'. It distinguishes from siblings like 'add', 'delete', and 'update' by focusing on retrieval. However, it doesn't explicitly contrast with siblings beyond the verb difference, so it's not a perfect 5.

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 for listing appointments with date filtering, but doesn't explicitly state when to use this tool versus alternatives like 'calcom_add_appointment' or provide context on prerequisites. It mentions filtering by date range, which gives some guidance, but lacks explicit when/when-not instructions or named alternatives.

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