Routine
OfficialServer 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authProfileC | Main user identity. |
| calendarAllC | All calendars. |
| calendarGetD | A calendar. |
| eventDayD | The events on a given day. |
| eventGetD | An event. |
| eventTimelineC | Agenda view for a day. |
| pageAllD | All pages. |
| pageGetD | Get a page. |
| peopleByEmailC | The potential contact owning this email address. |
| peopleGetD | The contact with the given id. |
| taskCompleteD | Complete a task. |
| taskCreateSimpleA | Create a task (simplified for MCP). Usually you only need to pass the title. Do not try to pass the integration_id or distant_task_id. |
| taskDayC | Tasks of a day sorted by: starred < default < (completed or ignored). |
| taskGetD | A task. |
| taskUncompleteD | Uncomplete a task. |
| taskUpcomingC | Non-allocated organized by week and sorted alphabetically. |
| taskUnplannedC | Unplanned tasks. |
| taskUpdateD | Patch a task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| help |
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes, but there is some overlap between eventDay and eventTimeline (both provide daily event views) and between taskDay, taskUnplanned, and taskUpcoming (all list tasks with different filters). The descriptions help differentiate them, but an agent might occasionally misselect between these similar tools.
The naming is mostly consistent with a verb_noun pattern (e.g., calendarGet, eventGet, taskCreateSimple), but there are minor deviations like authProfile (noun_noun), calendarAll (noun_adjective), and peopleByEmail (noun_preposition_noun). These deviations are readable but break the overall pattern slightly.
With 18 tools, the count is slightly high but reasonable for a productivity/calendar domain covering calendars, events, pages, people, and tasks. It feels comprehensive rather than bloated, though it borders on being heavy for an MCP server.
The tool set provides complete CRUD/lifecycle coverage for its domains: calendars (list, get), events (list by day, get, timeline), pages (list, get), people (get by email/id), and tasks (create, get, update, complete/uncomplete, list by various filters). There are no obvious gaps, and agents can handle typical workflows without dead ends.