list_calendar_events

Retrieve macOS Calendar events for any date range to review schedules, check availability, and manage appointments.

Instructions

List calendar events for a date range

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)
The list_calendar_events tool is registered here as part of a loop that registers all tools. This is a stub implementation for Glama inspection purposes - the actual implementation is in a native macOS binary.
```
for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}
```

Tool Definition Quality

B3/5.0

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. While it mentions 'date range', it does not explain how to specify the range given the empty parameter schema, which calendar(s) are queried, or what the return format/pagination behavior is.

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 a single, efficient sentence with no wasted words. However, given the ambiguity regarding the calendar system and the mismatch between the 'date range' mention and empty parameter schema, it borders on under-specification rather than optimal conciseness.

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

Completeness2/5

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

The description is incomplete given the tool's contextual complexity. It lacks explanation of the return values (no output schema exists), does not clarify which calendar source is used, and fails to address the discrepancy between the 'date range' functionality described and the empty input schema.

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 input schema contains zero parameters. According to calibration guidelines, 0 parameters establishes a baseline score of 4. The description mentions 'date range' implying parameters might be expected, but this does not change the baseline for the empty schema.

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 lists calendar events and specifies the scope is limited to a date range. However, it fails to distinguish from sibling tool 'outlook_list_events', leaving ambiguity about which calendar system (Apple Calendar vs. Outlook) is being accessed.

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?

No guidance is provided on when to use this tool versus 'outlook_list_events' or other calendar-related siblings. There is no mention of prerequisites, default calendar selection, or how to handle multiple calendar accounts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Pilot MCP