Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

List calendar events

list_calendar_events
Read-onlyIdempotent

List calendar events and recurring occurrences within a start/end window to check schedules, busy/free time, locations, attendees, and organizer details.

Instructions

Read the user’s calendar, agenda or schedule — what’s on their calendar, what meetings they have, when they are busy or free. With a start/end window (ISO 8601 with offset, both or neither; end exclusive, so a day runs to the next midnight), lists every event and every occurrence of a repeating series that falls inside it, each at its actual date and time; a moved occurrence says when it originally was. Without a window it lists each stored event once, a series at its first occurrence with its repeat rule — use a window to answer "what is on day X". Each entry has its title, time (dates only for all-day events), location, "showAs: free" on an event that does not count as busy time (every other event is busy), reminders, organizer (marked "(you)" when it is the user), attendees with their response status for that occurrence, uid, and for an occurrence its recurrenceId and the rule of the series it belongs to (repeats). Pass the uid (and recurrenceId, to touch one occurrence only) to update_calendar_event or delete_calendar_event; the returned attendee list is the current membership those tools edit, so read it here before removing or adding attendees rather than guessing. Defaults to the user’s default calendar. Birthdays are not calendar events here; for upcoming birthdays use list_upcoming_birthdays.

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": "list_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
calendarUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is low, yet the description still adds real behavior: end-exclusive windows, repeating-series expansion with actual occurrence times, moved-occurrence original times, showAs:free semantics, and default-calendar fallback. It does not discuss result size limits or pagination for very large windows, which is the one operational gap.

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?

Front-loads purpose and mode selection before the dense return-value inventory, and nearly every clause carries information (recurrenceId, attendee responses, showAs). It is a single long run-on paragraph, however, and would scan faster split into window-mode / no-window-mode / return-shape bullets.

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?

With no output schema, the description fully inventories the returned fields (title, time, location, showAs, reminders, organizer, attendee statuses, uid, recurrenceId) and explains how occurrences differ from series entries. Combined with the mode semantics, an agent has everything needed to call and interpret it correctly.

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?

Schema coverage is 0%, so the description must carry the load: it explains start/end as ISO 8601 with offset, that both or neither are required, and that end is exclusive. The third parameter (calendarUrl) is only hinted at via 'Defaults to the user's default calendar' and is never named or explained, leaving a gap that matters given the empty schema docs.

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?

Opens with a concrete verb and resource plus synonyms an agent is likely to see in user phrasing ('calendar, agenda or schedule'). It also distinguishes itself from siblings by naming list_upcoming_birthdays for birthdays and pointing to update/delete tools for follow-on actions.

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 the two modes (with a start/end window vs. without) and the condition selecting each: 'use a window to answer "what is on day X"'. It also tells the agent to read attendees here before editing them via update/delete rather than guessing.

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