gcal-fast-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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_calendarsA | List all calendars the user has access to. Returns JSON array. |
| get_calendarA | Get details of a specific calendar. |
| list_eventsA | List calendar events within a time range. Returns JSON array of events. |
| get_eventB | Get full details of a single calendar event. |
| create_eventC | Create a new calendar event. |
| update_eventB | Update an existing calendar event. Only provided fields are changed. |
| delete_eventC | Delete a calendar event. |
| quick_addA | Create an event from a natural language string using Google's NLP parser. |
| check_availabilityA | Check free/busy status for one or more calendars. Returns busy time ranges per calendar. |
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 9 tools
Each tool targets a distinct resource+action combination: calendars vs events are clearly separated, and get/list/create/update/delete are unambiguous. quick_add and check_availability are additional distinct operations. Only slight potential confusion exists between list_events and check_availability, though they serve different purposes (event detail vs busy windows).
All tools follow a consistent verb_noun pattern: list_calendars, get_calendar, list_events, get_event, create_event, update_event, delete_event. quick_add and check_availability deviate slightly but are well-established domain terms that read naturally and don't break the overall pattern.
Nine tools is well within the ideal 3-15 range. Each tool serves a meaningful purpose for a Google Calendar MCP server: full CRUD on calendars and events, plus two useful extras (NLP quick add and availability checking). No tool feels redundant or padding.
The surface provides full lifecycle coverage for both calendars (list, get) and events (list, get, create, update, delete). quick_add and check_availability round out common user workflows. Missing operations like moving events or managing reminders are minor and not core to basic calendar operations.