MCP server for Google Calendar integration, enabling calendar management, event creation, editing, and retrieval through AI assistants
Server has 6 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-100 chars, mostly adequate), and input schemas are present with type definitions. However, parameter descriptions are sparse or missing context. Output schemas are undocumented, LLMs cannot predict what fields to expect from responses. Error handling is absent from visible code. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Naming is verb-first and clear (get_, add_, edit_, delete_), following conventions well. The server lacks pagination guidance, output field documentation, and recovery hints for common failures.
Add an event to a calendar
Delete an event from a calendar
Edit an event from a calendar
List all calendars for the user
Get Events from all calendars for a specific period or for the current day if no end period is provided
Get Events from a specific calendar for a specific period or for the current day if no end period is provided
Output schemas completely undocumented. LLMs cannot predict response structure, field names, or types. Responses from get-calendars, get-events, add-event, edit-event, delete-event lack documented return types.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. delete-event is DESTRUCTIVE, add-event and edit-event are WRITE, these must be annotated so agents understand irreversibility.
Parameter descriptions lack actionable constraints. 'startDateString' and 'startDate' have minimal guidance on format (ISO 8601? natural language?). No examples, patterns, or validation rules visible. LLMs will guess formats and fail.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
No error handling or recovery guidance in visible code. Agents have no way to know if a failure is retryable, user-fixable, or fatal. No guidance on what to do if a calendar ID is invalid or an event already exists.
Pagination not addressed. get-events and get-events-from-calendar could return hundreds of events for a date range, but no limit, offset, or cursor parameters visible. Large result sets will exhaust context windows.