Skip to main content
Glama

Build an ics calendar

build_ics

Generate a valid .ics calendar file from dated events and recurring classes with reminders, skipping holidays and reading weeks so schedules import correctly.

Instructions

Build a valid .ics calendar file from dated events and recurring classes, with reminders. Inputs: events (each with title, date, optional start_time, end_time, type, course, location and notes), classes (each with course, weekdays, start_date, end_date, start_time and optional end_time, location, holidays and reading_weeks), reminders_minutes (whole minutes before each event, default 60), calendar_name, optional timezone and optional output_path. Pass timezone as an IANA name such as America/Toronto so timed events keep the right hour in Google Calendar, Apple Calendar and Outlook. Each class becomes one weekly recurring event with holidays and reading weeks removed. The tool checks the file before returning it. Example prompt: "Make an .ics file for my course with a reminder one day before each assignment."

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

Input Schema

NameRequiredDescriptionDefault
eventsNoDated events such as assignments and exams.
classesNoRecurring classes to add as weekly events.
timezoneNoIANA time zone name for timed events, such as America/Toronto. Without it, times have no zone and calendar apps use their own.
output_pathNoOptional file path for the .ics file. The folder must already exist because folders are not created. Leave it out to get the calendar text back instead.
calendar_nameNoName shown in the calendar app. Defaults to "Course calendar".
reminders_minutesNoReminder times in whole minutes before an event. Defaults to [60]. Pass an empty array for no reminders.

Output Schema

NameRequiredDescriptionDefault
icsYesThe calendar file as text, with CRLF line breaks.
validYesTrue when the calendar passed the built in checks.
errorsYesProblems found by the checks. Empty when the calendar is valid.
class_countYesHow many recurring classes the calendar holds.
event_countYesHow many single events the calendar holds.
output_pathYesThe file path the calendar was written to, or null when no path was passed.
class_meetingsYesHow many class meetings the recurring events produce after skips.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / output_path / description
      Previous value: -"Optional file path. When it is passed, the calendar is written there as a .ics file."New value: +"Optional file path for the .ics file. The folder must already exist because folders are not created. Leave it out to get the calendar text back instead."
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA time zone name for timed events, such as America/Toronto. Without it, times have no zone and calendar apps use their own.",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare a non-read-only, closed-world operation, and the description adds useful behavior: file validation before return, recurring-class expansion with holidays and reading weeks removed, timezone portability across calendar apps, and text output when output_path is omitted. It still does not say whether an existing output_path file is overwritten, which is a relevant gap for a file-writing tool.

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 first sentence front-loads purpose, and the description is organized around inputs, timezone behavior, recurrence behavior, validation, and an example. It is somewhat dense and duplicates the schema's parameter inventory, but the content is largely useful and appropriately sized for a nontrivial calendar-generation tool.

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?

Given six parameters, nested event and class arrays, annotations, and an output schema, the description covers the important behavior an agent needs: what gets built, how classes recur, how holidays and reading weeks are handled, timezone guidance, reminders, and output_path fallback. No critical return-value explanation is needed because an output schema exists.

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 100%, so the schema already defines all six parameters in detail, and the description mostly repeats that field list. It does add some meaning beyond the schema, especially that each class becomes one weekly recurring event with holidays and reading weeks removed, plus practical timezone and reminder defaults.

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 states a specific verb and resource: build a valid .ics calendar file from dated events, recurring classes, and reminders. This clearly distinguishes it from siblings like extract_schedule_events, merge_calendars, and expand_recurring_classes.

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?

It gives a clear usage context and an example prompt for making an .ics file with reminders. It does not explicitly name when to prefer a sibling tool or when not to use this one, so it falls short of full alternative routing.

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