Fastmail MCP Server

get_calendar_events

Retrieve calendar events within a date range. Optionally filter by calendar ID or title text to find specific events.

Instructions

Get calendar events within a date range. Optionally filter by calendar ID or search text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_calendar_events"
  }
}

Input Schema

Name	Required	Description
`after`	No	Only events starting after this date/time (ISO 8601, e.g. 2024-01-15 or 2024-01-15T09:00:00)
`limit`	No	Maximum number of events to return (default 50, max 100)
`title`	No	Filter events by title text (partial match)
`before`	No	Only events starting before this date/time (ISO 8601, e.g. 2024-02-15 or 2024-02-15T17:00:00)
`calendarId`	No	Filter to a specific calendar ID from list_calendars. Returns events from all calendars if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of conveying safety. The verb 'Get' suggests a read-only operation, but the description does not explicitly state that it does not modify events or disclose behaviors like default ordering or date inclusivity. It adds the date-range scoping but lacks richer behavioral context.

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?

A single, well-structured sentence that conveys the core purpose and options without waste. Every word earns its place.

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

Completeness4/5

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

With five optional parameters fully documented in the schema and no output schema, the description gives a high-level overview sufficient for an agent to decide to invoke it. It could mention limit/pagination, but the schema already covers parameter specifics, so the description is adequately complete for the complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all five parameters. The description mentions 'calendar ID or search text' but does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 tool's function: 'Get calendar events within a date range' with optional filters. The verb 'Get' paired with the resource 'calendar events' is specific and distinguishes it from the sibling tool get_calendar_event, which retrieves a single event.

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

Usage Guidelines4/5

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

The description implies usage for listing events in a range and mentions optional filters, giving clear context. However, it does not explicitly mention when to prefer alternatives like get_calendar_event for a single event, so it stops short of providing exclusions.

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