Loading ToolBench

Reading the current corpus…

google-suite-mcp MCP server · D · ToolBench

← Browse

google-suite-mcp

github.com/goyalsandeep2k/google-suite-mcp

MCP server for personal Google accounts — Drive, Docs, Sheets, Slides, Gmail, and Calendar

2026-07-28+STDIO29 tools

54/100

Definition Quality72

Protocol Readiness50

Supportability25

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

Google Suite MCP provides 29 tools across Drive, Docs, Sheets, Slides, Gmail, and Calendar with consistent naming (verb_noun pattern) and complete input schemas. However, descriptions are generic and lack LLM-optimization guidance. Parameter descriptions are minimal (often single phrases). Output schemas are not documented. Error handling is basic (generic JSON stringification). Tool composition is sound but lacks idempotency hints and confirmation patterns for destructive operations.

Tools (29)

calendar_create_eventwriteauthsource verified75/100

Create a new calendar event

calendar_get_eventread onlyauthsource verified72/100

Get details for a specific calendar event

calendar_list_calendarsread onlyauthsource verified68/100

List all calendars in the user's Google Calendar account

calendar_list_eventsread onlyauthsource verified72/100

List upcoming calendar events

calendar_update_eventwriteauthsource verified72/100

Update an existing calendar event

docs_append_textwriteauthsource verified72/100

Append text to the end of a Google Doc

docs_createwriteauthsource verified72/100

Create a new Google Doc

Issues (5)

HIGHconfirmation-request ↗

Destructive operations (drive_delete_file, slides_delete_slide) lack confirmation/dry-run patterns. No guidance for LLM to verify intent before irreversible action.

drive_delete_fileslides_delete_slide

HIGHresponse-shaper ↗

Output schemas not documented. LLMs cannot predict response structure for downstream tool chaining. E.g., drive_list_files returns file objects but schema omits field names (id, name, mimeType, etc.).

drive_list_filesdrive_searchsheets_get_valuesgmail_searchcalendar_list_events

HIGHconstrained-input ↗

Parameter descriptions are minimal (1-3 words). Lack format constraints, ranges, and LLM guidance. E.g., 'pageSize' has no min/max; 'query' has no syntax hints for Drive query language.

drive_list_filesdrive_searchsheets_update_valuescalendar_list_events

Recommendations

Expand tool descriptions to 50-200 chars with WHEN/WHY guidance. E.g., 'Search Gmail by sender, subject, or date range. Use this when you know partial criteria; use gmail_get_message if you have a message ID.'
Document output schemas for all tools. Include field names, types, and sample values. E.g., drive_list_files returns [{id, name, mimeType, createdTime, owners}].
Add format constraints and ranges to parameters. E.g., pageSize: 1-1000 (default 20); query: 'Drive query syntax: name contains "X", mimeType="...", trashed=false'.
Implement confirmation pattern for destructive tools. Add optional 'dryRun' parameter or require explicit confirmation via a separate confirm_delete_file tool.
Enhance error responses with actionable guidance. E.g., 'File not found (404). Try drive_search() to locate the file by name, or verify the fileId is correct.'

Score history

Overall score trend

First recorded score · v2 rubric

54/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	54	2026-07-28+	v2