Skip to main content
Glama

get_my_contact_lists

Retrieve contact lists from CalDAV, CardDAV, and WebDAV services linked to Fastmail or Apple iCloud accounts using the DAV MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler that authenticates with CardDAV client and fetches the list of user's contact address books (contact lists). Returns JSON of address books.
    async () => {
      if (!cardDavClient) return { content: [{ type: "text", text: "CardDAV client not initialized for this provider."}], isError: true };
      try {
        await cardDavClient.login();
        const addressBooks = await cardDavClient.fetchAddressBooks();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(addressBooks, null, 2)
          }]
        };
      } catch (error) {
        console.error(`Error in get_my_${DAV_PROVIDER}_contact_lists:`, error);
        return {
          content: [{
            type: "text",
            text: `Error listing address books: ${JSON.stringify(error.message || error)}`
          }],
          isError: true
        };
      }
    }
  • index.js:161-189 (registration)
    Tool registration for 'get_my_contact_lists' (dynamic name: get_my_${DAV_PROVIDER}_contact_lists). No input schema required. Called 'get_my_contact_lists' in descriptions.
    server.tool(
      `get_my_${DAV_PROVIDER}_contact_lists`,
      {
        description: `Lists all of your contact address books from your ${DAV_PROVIDER} account. It returns a list of address book objects, each with details like its URL and name. Use this to find the \`addressBookUrl\` needed for fetching contacts.`,
        inputSchema: {}
      },
      async () => {
        if (!cardDavClient) return { content: [{ type: "text", text: "CardDAV client not initialized for this provider."}], isError: true };
        try {
          await cardDavClient.login();
          const addressBooks = await cardDavClient.fetchAddressBooks();
          return {
            content: [{
              type: "text",
              text: JSON.stringify(addressBooks, null, 2)
            }]
          };
        } catch (error) {
          console.error(`Error in get_my_${DAV_PROVIDER}_contact_lists:`, error);
          return {
            content: [{
              type: "text",
              text: `Error listing address books: ${JSON.stringify(error.message || error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Schema reference in related tool 'get_contacts_from_${DAV_PROVIDER}_list' that mentions 'get_my_contact_lists' as source for addressBookUrl.
      inputSchema: {
        addressBookUrl: z.string().describe("The unique identifier (URL) of the contact list from which to fetch contacts. You can get this from 'get_my_contact_lists'."),
      },
    },
  • Initialization of CardDAV client used by the contact lists tool (Fastmail-specific block). Similar for iCloud at lines 68-73.
    cardDavClient = new DAVClient({
      serverUrl: cardDavServerUrl,
      credentials: { username: DAV_USERNAME, password: DAV_PASSWORD },
      authMethod: "Basic",
      defaultAccountType: "carddav",
    });
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