Skip to main content
Glama
limey

cal-scheduler

by limey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CAL_DEFAULT_TZNoIANA zone every event is stored inPacific/Auckland
CALDAV_BASE_URLYesCalDAV server URL, e.g. http://127.0.0.1:5232
CALDAV_PASSWORDNoCalDAV account password
CALDAV_USERNAMENoCalDAV account user

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_calendarsA

List the calendars available on the account.

create_calendarB

Create a new calendar by display name.

delete_calendarA

Delete a calendar and all of its events. Irreversible.

list_eventsA

List event occurrences in [start, end], expanding recurring series.

Dates are interpreted in the calendar's configured zone. Returns one entry per
occurrence (recurring instances are expanded), sorted by start.
resolve_datetimeA

Show how a datetime string will be interpreted, without writing anything.

Use this to confirm a zone before committing an event.

create_eventA

Create an event (single, or recurring if rrule is given).

`start`/`end` are ISO 8601 (see parameter docs for zone + default-duration
details — read those before writing). `rrule` is a raw RRULE body,
e.g. "FREQ=WEEKLY;COUNT=12". `calendar` is required in practice — there
is no default calendar. Pick deliberately; events are not validated
against calendar type.
update_eventA

Edit a whole event/series. Only the fields you pass change.

Preserves the UID and any single-occurrence exclusions/overrides. If you move
`start` without giving `end`, the duration is kept. Moving `start` re-anchors
the whole series — occurrences before the new start stop being generated (this
retimes an entire series; it does not split one at a date).
delete_eventA

Delete a whole event/series (and any of its overrides). Irreversible.

mark_doneA

Mark an event (or one occurrence of a series) done at the current UTC moment.

`occurrence=None` marks the whole event / series; otherwise marks only that
occurrence (via a RECURRENCE-ID override). Idempotent: re-marking replaces
the prior timestamp. The response includes `series_remaining` and
`overrides` for parity with move_occurrence / exclude_occurrence.
exclude_occurrenceA

Drop a single occurrence of a recurring series (EXDATE).

`occurrence` is the instance's current start exactly as returned by
`list_events`, including the UTC offset (e.g. `2026-06-18T09:00:00+12:00`).
Bare local times may not match. The response includes `series_remaining`
(occurrences left in the series) and `overrides` (RECURRENCE-ID overrides
on the series) so the rest-of-series-unchanged claim is observable.
move_occurrenceA

Reschedule a single occurrence of a series (RECURRENCE-ID override).

`occurrence` is the instance's current start exactly as returned by
`list_events`, including the UTC offset (e.g. `2026-06-18T09:00:00+12:00`).
Bare local times may not match. `new_start`/`new_end` are where it moves to.
Omit `new_end` to keep the occurrence's existing duration. The rest of the
series is unchanged. The response includes `series_remaining` (occurrences
left in the series) and `overrides` (RECURRENCE-ID overrides on the series)
so the rest-of-series-unchanged claim is observable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a distinct resource and action: calendar CRUD, event CRUD, occurrence-level operations (exclude, move), done-status marking, and datetime resolution. Even update_event vs move_occurrence are unambiguous due to explicit scope differentiation (whole event/series vs single occurrence).

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (list_calendars, create_event, exclude_occurrence). mark_done is a minor variation (verb+adverb) but still fits the naming style and does not disrupt the pattern.

Tool Count5/5

11 tools is well-scoped for a calendar/scheduler server, covering calendar management, event management, and recurring-event operations without unnecessary redundancy. Each tool earns its place.

Completeness4/5

Core lifecycle for calendars (list/create/delete) and events (list/create/update/delete) is covered, along with advanced recurrence handling. Missing calendar update (e.g., rename) is a minor gap, but agents can work around it by recreate if needed.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources