Skip to main content
Glama
NOVA-3951

Fastmail Calendar MCP Server

list_calendars

Read-onlyIdempotent

Retrieve all calendars from a Fastmail account to identify and access specific calendars for managing events.

Instructions

STEP 1 - ALWAYS CALL THIS FIRST. Lists all calendars in the user's Fastmail account. Returns an array of calendars with displayName (human-readable name like "Work", "Personal", "Family"), url (required for other operations), and timezone. You MUST call this before list_events, create_event, update_event, or delete_event to get the calendar URL. Look at the displayName to identify which calendar the user wants (e.g., "Work" for work schedule, "Personal" for personal events).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execution handler for the list_calendars tool. It checks if in test mode and returns mock calendars, otherwise maps the fetched calendars to a simple object with displayName, url, description, timezone and returns as JSON text.
    case "list_calendars": {
      if (isTestMode) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                _testMode: true,
                _message: "Demo mode - showing sample calendars. Use real Fastmail credentials for actual data.",
                calendars: MOCK_CALENDARS,
              }, null, 2),
            },
          ],
        };
      }
      
      const calendarList = calendars.map((cal) => ({
        displayName: cal.displayName,
        url: cal.url,
        description: cal.description || "",
        timezone: cal.timezone || "",
      }));
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(calendarList, null, 2),
          },
        ],
      };
    }
  • src/index.ts:245-260 (registration)
    The tool registration entry in the list of tools returned by ListToolsRequestSchema, including name, description, input schema (no parameters), and annotations indicating it's read-only and idempotent.
    {
      name: "list_calendars",
      description: `STEP 1 - ALWAYS CALL THIS FIRST. Lists all calendars in the user's Fastmail account. Returns an array of calendars with displayName (human-readable name like "Work", "Personal", "Family"), url (required for other operations), and timezone. You MUST call this before list_events, create_event, update_event, or delete_event to get the calendar URL. Look at the displayName to identify which calendar the user wants (e.g., "Work" for work schedule, "Personal" for personal events).`,
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
      annotations: {
        title: "List Calendars",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
    },
  • The input schema definition for the list_calendars tool, specifying an empty object with no required properties.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
  • Mock calendar data used by the list_calendars handler in test/demo mode.
    const MOCK_CALENDARS = [
      {
        displayName: "Personal",
        url: "https://caldav.fastmail.com/dav/calendars/user/demo@fastmail.com/personal/",
        description: "Personal calendar for everyday events",
        timezone: "America/New_York",
      },
      {
        displayName: "Work",
        url: "https://caldav.fastmail.com/dav/calendars/user/demo@fastmail.com/work/",
        description: "Work meetings and deadlines",
        timezone: "America/New_York",
      },
      {
        displayName: "Family",
        url: "https://caldav.fastmail.com/dav/calendars/user/demo@fastmail.com/family/",
        description: "Family events and activities",
        timezone: "America/New_York",
      },
    ];
Behavior4/5

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

Annotations already cover safety (readOnlyHint: true, destructiveHint: false) and idempotency, but the description adds valuable behavioral context: that this returns an array with specific fields (displayName, url, timezone), that the URL is required for other operations, and practical interpretation guidance. No contradiction with annotations.

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?

Well-structured with clear step-by-step guidance, but slightly verbose with repetition of 'calendar' and could be more front-loaded. Every sentence adds value, but some phrasing could be tighter.

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

Completeness5/5

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

For a zero-parameter tool with comprehensive annotations, the description provides complete context: clear purpose, explicit prerequisites, output structure explanation, and practical usage guidance. No output schema exists, so the description appropriately explains what's returned.

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

Parameters4/5

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

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on output semantics and usage context.

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 ('Lists all calendars') and resource ('in the user's Fastmail account'), and distinguishes it from siblings by explaining its prerequisite role for other calendar operations. It provides concrete examples of calendar types like 'Work' and 'Personal'.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('ALWAYS CALL THIS FIRST' before list_events, create_event, update_event, or delete_event) and why (to get the calendar URL). It also provides guidance on how to interpret results ('Look at the displayName to identify which calendar the user wants').

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/NOVA-3951/Fastmail-Calendar-MCP'

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