MCP server for interacting with Google Calendar
The server defines 6 tools with complete JSON Schema input definitions and basic descriptions. However, there are significant gaps in description quality, parameter documentation, output schema documentation, and error handling guidance. Tool names follow verb_noun conventions, which is positive. Schemas are present and include type information, but descriptions lack the depth and LLM-optimization guidance required for confident tool selection. Most parameters have descriptions, but lack constraint documentation (ranges, patterns, valid values). No output schemas are documented. Error handling provides no recovery guidance. This is typical of community MCP servers and falls in the 'fair to poor' range.
Create a calendar event
Delete a calendar event
Edit a calendar event
Get a calendar event
Get events from a calendar
List all calendars
Descriptions are too short and lack LLM-optimization. Tool descriptions like 'List all calendars' (18 chars), 'Get a calendar event' (21 chars), and 'Delete a calendar event' (23 chars) fall below the 50-char minimum for effective LLM reasoning. No description answers WHAT the tool does in context, WHEN to use it vs similar tools, or WHAT it returns.
No output schemas are documented. The codebase returns JSON (verified in handlers.ts: 'JSON.stringify()'), but tool definitions do not declare the response structure. LLMs cannot plan downstream calls or extract specific fields without knowing the output schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 45 | - | v1 |
Missing constraint documentation on date parameters. Params like 'startsAt' and 'endsAt' (list_calendar_events) specify format YYYY-MM-DD in description text, but lack type declaration as 'string' with 'format': 'date' in schema. create_calendar_event and edit_calendar_event similarly underdocument date constraints.
Destructive tool (delete_calendar_event) lacks confirmation/dry-run pattern. No recovery guidance in description. LLMs may invoke deletion without warning, and no error response guides the LLM on recovery steps if deletion fails.
Parameter descriptions lack constraint and validation guidance. E.g., 'colorId' in create_calendar_event and edit_calendar_event has no description of valid color IDs (what are the valid values? is it an enum?). LLMs will hallucinate invalid color values.
No error handling guidance. Error responses in handlers.ts just return JSON.stringify of errors. LLMs receive no actionable recovery hints (e.g., 'Calendar not found. Try list_calendars() to find valid calendar IDs'). [Source: pattern:recovery-guide]
Pagination info sparse. list_calendars accepts pageToken parameter but description says nothing about expected pagination behavior, total counts, or when pagination is exhausted. list_calendar_events similarly underdocuments pagination semantics.
No documentation of required vs optional parameters in create/edit event tools. The 'event' object nested structure makes it unclear to LLMs whether 'summary', 'description', 'start', 'end' are always required or can be omitted in edit operations. Nested required arrays are hard for LLMs to parse.