calendula
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDULA_TTL_MINUTES | No | Change the cache TTL of 1 hour for fetched calendar days (in minutes). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Reads the user's Outlook (classic) calendar on Windows, from WSL. Read-only.
Events for today and later are reused for up to 60 minutes after they were fetched; past days are fetched once per session. Every answer says when it was fetched. Pass refresh=true when the user says the calendar has just changed, or when an exact, current answer matters.
Dates are YYYY-MM-DD in the user's local time. Turn words like "tomorrow" or "next Monday" into dates first.
If fetching fails, report the error. Never fill in events from memory or from older answers.
If the error says Outlook's COM connection is broken, ask the user for permission before calling restart_outlook (it force-quits Outlook and unsaved drafts are lost), then retry once. Do not restart repeatedly.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_eventsA | List events (time, subject, location) day by day. Use get_event for attendees and the body. |
| get_eventA | Details of the event at a time: location, organizer, attendees, status, and the body. If no event is running at that time, returns the timed event that starts nearest to it (and says so). |
| restart_outlookA | Force-quit Outlook (classic) and start it again, to recover a broken COM connection. Unsaved drafts are lost. Call it only after the user has agreed, and only after a fetch failed with a COM error. |
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 3 tools
list_events (day-by-day summaries) and get_event (full details for a specific time) have a clear summary-vs-detail split, and restart_outlook is unmistakably a maintenance operation. The only mild blur is get_event's fallback of returning the nearest starting event, which makes it behave slightly like a lookup rather than a strict fetch, but the description calls this out explicitly.
All three tools follow a clean verb_noun snake_case pattern: list_events, get_event, restart_outlook. No mixed conventions or vague verbs, and the naming maps directly onto the described action.
Three tools is a deliberate, well-scoped surface for a read-only Outlook calendar reader plus one recovery utility; nothing feels redundant. It is on the thin side of the typical 3-15 range, but each tool clearly earns its place.
The surface covers reading a day's events and drilling into one event, but there are notable gaps: no create/update/delete or RSVP/response operations, no cross-calendar search or range queries beyond day-by-day listing, and no way to list available calendars. Agents needing to modify a calendar will hit a dead end.