Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_calendar_events

Retrieve events from Fastmail calendars using optional date range, calendar ID, and limit filters to view your schedule.

Instructions

List events from a calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return (default: 50)
endDateNoFilter events ending before this date (ISO 8601, e.g. 2026-03-30T00:00:00Z)
startDateNoFilter events starting from this date (ISO 8601, e.g. 2026-03-23T00:00:00Z)
calendarIdNoID of the calendar (optional, defaults to all calendars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.1
    • addedInput schema / properties / endDate
      Added value: +{
+  "description": "Filter events ending before this date (ISO 8601, e.g. 2026-03-30T00:00:00Z)",
+  "type": "string"
+}
    • addedInput schema / properties / startDate
      Added value: +{
+  "description": "Filter events starting from this date (ISO 8601, e.g. 2026-03-23T00:00:00Z)",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it provides none. Missing details on pagination, ordering, timezone handling, or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only one sentence, which is efficient but too brief for a tool with 4 parameters and many siblings. Could include more context without being verbose.

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?

Lacks completeness: no mention of return fields, default behavior when calendarId is omitted, or limitations. For a listing tool with date filters, more context is needed.

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?

Input schema has 100% description coverage with clear parameter details. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 it lists events from a calendar, but does not specify the scope (e.g., single calendar or all) or differentiate from sibling tools like get_calendar_event.

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 on when to use this tool vs alternatives such as get_calendar_event or search_emails. Missing context on prerequisites or default behavior.

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

Deploy Server

Other Tools