Google Calendar - No deletion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google Cloud OAuth client ID | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google Cloud OAuth client secret | |
| GOOGLE_REFRESH_TOKEN | Yes | Your Google OAuth refresh token |
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 |
|---|---|
| list_emailsB | List recent emails from Gmail inbox |
| search_emailsC | Search emails with advanced query |
| send_emailC | Send a new email |
| modify_emailA | Modify email labels (archive, trash, mark read/unread) |
| list_eventsC | List upcoming calendar events |
| create_eventC | Create a new calendar event |
| meeting_suggestionC | Suggest available meeting slots within the next 30 days |
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 7 tools
The tool set mixes calendar and email operations without clear boundaries, causing potential misselection. For example, 'list_emails' and 'search_emails' overlap in purpose for email retrieval, while calendar tools like 'create_event' and 'list_events' are distinct but the server's dual-domain focus creates confusion.
Naming conventions are mixed, with some tools using verb_noun patterns like 'create_event' and others using noun_verb like 'meeting_suggestion'. While readable, the inconsistency in structure (e.g., 'modify_email' vs. 'send_email') deviates from a predictable pattern.
With 7 tools, the count is reasonable, but it feels borderline due to the server's split focus on both Google Calendar and Gmail. This scope might be too broad for the limited tool set, leading to a thin coverage in each domain.
For the implied dual-domain purpose, there are significant gaps. In calendar, tools lack update or delete event operations, and in email, there's no way to delete emails or manage drafts. The server name suggests calendar focus, but email tools are included without full lifecycle coverage.