Skip to main content
Glama

get_my_calendars

Retrieve and manage CalDAV calendars from Fastmail and Apple iCloud accounts using the DAV MCP Server, enabling efficient organization and access to your scheduling data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:82-110 (registration)
    Registration of the tool named `get_my_${DAV_PROVIDER}_calendars` (e.g., get_my_fastmail_calendars or get_my_icloud_calendars), which lists all calendars from the DAV provider. This tool is referred to as 'get_my_calendars' in descriptions and other tool schemas.
    server.tool(
      `get_my_${DAV_PROVIDER}_calendars`,
      {
        description: `Lists all available calendars from your ${DAV_PROVIDER} account. It returns a list of calendar objects, each containing details like its URL, name, and other properties. Use this to find the \`calendarUrl\` for other calendar-related tools.`,
        inputSchema: {}
      },
      async () => {
        if (!davClient) return { content: [{ type: "text", text: "CalDAV client not initialized for this provider."}], isError: true };
        try {
          await davClient.login();
          const calendars = await davClient.fetchCalendars();
          return {
            content: [{
              type: "text",
              text: JSON.stringify(calendars, null, 2)
            }]
          };
        } catch (error) {
          console.error(`Error in get_my_${DAV_PROVIDER}_calendars:`, error);
          return {
            content: [{
              type: "text",
              text: `Error listing calendars: ${JSON.stringify(error.message || error)}`
            }],
            isError: true
          };
        }
      }
    );
  • index.js:88-109 (handler)
    The handler function for the calendars tool: logs into the CalDAV client, fetches the list of calendars using davClient.fetchCalendars(), and returns them as JSON. Handles errors appropriately.
    async () => {
      if (!davClient) return { content: [{ type: "text", text: "CalDAV client not initialized for this provider."}], isError: true };
      try {
        await davClient.login();
        const calendars = await davClient.fetchCalendars();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(calendars, null, 2)
          }]
        };
      } catch (error) {
        console.error(`Error in get_my_${DAV_PROVIDER}_calendars:`, error);
        return {
          content: [{
            type: "text",
            text: `Error listing calendars: ${JSON.stringify(error.message || error)}`
          }],
          isError: true
        };
      }
    }
  • Input schema for the tool: empty inputSchema (no parameters required), with a detailed description.
    {
      description: `Lists all available calendars from your ${DAV_PROVIDER} account. It returns a list of calendar objects, each containing details like its URL, name, and other properties. Use this to find the \`calendarUrl\` for other calendar-related tools.`,
      inputSchema: {}
    },
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/jahfer/dav-mcp-server'

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