Skip to main content
Glama
xybstone

macOS Calendar MCP Server

by xybstone

list-calendars

Retrieve all available macOS calendars through direct integration with the Calendar application, enabling event management without OAuth setup.

Instructions

列出所有macOS日历

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the list-calendars tool by executing AppleScript to retrieve and format the list of macOS calendars.
    async listCalendars() {
      try {
        const script = `tell application "Calendar" to get name of calendars`;
        const result = execSync(`osascript -e '${script}'`, { encoding: 'utf8' });
        const calendars = result.trim().split(', ');
        
        return {
          content: [
            {
              type: 'text',
              text: `📅 可用日历 (${calendars.length}个):\n${calendars.map(cal => `• ${cal}`).join('\n')}`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`获取日历列表失败: ${error.message}`);
      }
    }
  • The handler function that implements the list-calendars tool by executing AppleScript to retrieve and format the list of macOS calendars.
    listCalendars() {
      try {
        const script = `tell application "Calendar" to get name of calendars`;
        const result = execSync(`osascript -e '${script}'`, { encoding: 'utf8' });
        const calendars = result.trim().split(', ');
        
        return {
          content: [{
            type: "text",
            text: `📅 可用日历 (${calendars.length}个):\n${calendars.map(cal => `• ${cal}`).join('\n')}`
          }]
        };
      } catch (error) {
        throw new Error(`获取日历列表失败: ${error.message}`);
      }
    }
  • The handler function that implements the list-calendars tool by executing AppleScript to retrieve and format the list of macOS calendars.
    listCalendars() {
      try {
        const script = `tell application "Calendar" to get name of calendars`;
        const result = execSync(`osascript -e '${script}'`, { encoding: 'utf8' });
        const calendars = result.trim().split(', ');
        
        return {
          content: [{
            type: "text",
            text: `📅 可用日历 (${calendars.length}个):\n${calendars.map(cal => `• ${cal}`).join('\n')}`
          }]
        };
      } catch (error) {
        throw new Error(`获取日历列表失败: ${error.message}`);
      }
    }
  • Input schema definition for the list-calendars tool (no parameters required).
    name: 'list-calendars',
    description: '列出所有macOS日历',
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false,
    },
  • Registration of the list-calendars handler in the tool call switch statement.
    case 'list-calendars':
      return await this.listCalendars();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('list') but doesn't describe what 'all' entails (e.g., scope, permissions, or format), whether it's read-only, or any side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence in Chinese that directly states the tool's function without any wasted words. It's front-loaded and appropriately sized for a simple listing tool.

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 low complexity (0 parameters, no annotations, no output schema), the description is minimally adequate but lacks depth. It covers the basic purpose but doesn't provide behavioral details or usage context, which could be helpful despite the simplicity. It meets the minimum for a straightforward tool but doesn't excel.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly implies no inputs are required, aligning with the schema. A baseline of 4 is appropriate for a parameterless tool.

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 verb ('列出' meaning 'list') and resource ('macOS日历' meaning 'macOS calendars'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'list-today-events' or 'list-week-events', which filter by time, but it's still specific about what it lists.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'list-today-events' or 'list-week-events', nor does it mention any prerequisites or exclusions. It's a basic statement of function without contextual usage advice.

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/xybstone/macos-calendar-mcp'

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