Model Context Protocol server providing secure access to Google Drive, Docs, Sheets, and Slides through MCP clients e.g. Claude Desktop
Scoring was not performed
Output schemas are not documented in tool definitions. While the server likely returns structured data, there is no visible schema specification for what fields agents should expect (e.g., list_files return format, get_file_info return fields). This forces agents to discover output structure at runtime and violates the pattern:tool requirement.
Parameter descriptions are minimal (15-30 chars) and lack actionable constraints. For example, 'pageSize' is described as 'Number of files to return per page' but does not specify valid range (e.g., 1-1000). 'cursor' for pagination lacks format guidance. 'exportMimeType' in download_file does not list valid MIME types. This violates pattern:constrained-input and review:param-validation-rules.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | F | 39 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 56 | 1.24.0+ | v1 |
Destructive tools (delete_file) and state-modifying tools (upload_file, create_*) lack error handling guidance. Tool descriptions do not explain recovery steps if a file is not found, quota is exceeded, or authentication fails. Agents are not told whether operations are idempotent or if retries risk duplicates. Violates pattern:recovery-guide and pattern:command-tool.
The delete_file tool accepts only fileId and offers no dry-run, confirmation step, or preview. This violates pattern:confirmation-request. A destructive operation should support confirmation or at least warn agents of irreversibility.
Parameters like 'localPath' (download_file) and 'filePath' (upload_file) are documented as accepting file paths but do not clarify whether they accept absolute paths, relative paths, or just filenames. The description does not hint at path validation or whether the tool will handle path traversal attacks. Violates review:param-validation-rules.