syllabus-calendar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_schedule_eventsA | Extract dated events from pasted syllabus text. Each line that names a date becomes one event, with a title, a type, a date and optional times. Inputs: text (the pasted syllabus or course schedule, one event per line), course (a course name or code to put on every event), year (the year to use when a date has no year) and term_start (the first day of the term, so a line such as Week 5: Midterm becomes an event). Titles are read from the words around the date, and each event is marked as an assignment, exam, quiz, lab, reading, class or other. Any line that has no date is returned in undated_lines instead of being dropped silently. The answer ends with a next step hint that points to build_ics when the events should become a calendar. When no line names a date, the count is 0 and the next step tells the student how to fix the pasted text. Example prompt: "Turn this syllabus into calendar events: Assignment 1 due Sep 15, Midterm exam October 20 at 10:00." |
| expand_recurring_classesA | Generate the meeting dates for a recurring class between two dates, and skip holidays and reading weeks. Inputs: course, weekdays (day names or codes such as Tuesday or TU), start_date, end_date, start_time, optional end_time, optional location, holidays (single dates or ranges) and reading_weeks (single dates or ranges). Returns every meeting date plus the dates that were skipped and why. The answer ends with a next step hint that points to build_ics when the class should become a calendar. Example prompt: "My biology class meets Tuesday and Thursday from Sep 8 to Dec 10, 2026 at 10:00. Skip the reading week of Oct 12 to Oct 16." |
| build_icsA | 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." |
| merge_calendarsA | Merge several course calendars into one and list timed events that overlap. Inputs: calendars (each with an optional name and an ics string), optional calendar_name and optional output_path. Events with the same UID are kept once. Weekly and daily recurring events are expanded when conflicts are checked. Example prompt: "Merge my three course calendars and tell me which classes conflict." |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role in the pipeline: parse text, build an .ics file, merge calendars, and preview recurring class dates. The only soft overlap is that build_ics internally expands recurring classes (holidays/reading weeks) while expand_recurring_classes exists as a separate preview step, so an agent could hesitate on which to use for recurrence handling.
All four names are snake_case and verb-first (extract_, build_, merge_, expand_), matching a clear verb_noun convention throughout. build_ics uses an acronym noun but still fits the same pattern.
Four tools map cleanly onto the parse → build → merge/preview workflow with no filler. The count is tight but each tool covers a necessary stage of the syllabus-to-calendar domain.
The core lifecycle is covered: text extraction, .ics generation with reminders and timezones, calendar merging with conflict detection, and recurrence expansion. Minor gaps exist around editing/inspecting existing events or importing an .ics for non-merge purposes, but the stated purpose is well served.