Loading ToolBench

Reading the current corpus…

google-mcp-multi-account MCP server · D · ToolBench

google-mcp-multi-account

github.com/elzinko/google-mcp-multi-account

MCP server for managing multiple Google Workspace accounts with Gmail and Drive access, featuring session-based access control, policy enforcement, and remote approval via passkey

2026-07-28+STDIO8 tools

56/100

Definition Quality76

Protocol Readiness35

Supportability38

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

Server defines 8 tools with complete JSON schemas and descriptions in French. All tools have input schemas with typed parameters and descriptions. However, descriptions are verbose (200-400+ chars) and lack LLM-optimized structure. Parameter descriptions are present but inconsistent in clarity. Output schemas are not documented. Error handling guidance is minimal. Session token management is a security concern, tokens appear as required parameters rather than server-side injection. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Naming is verb-noun compliant (list_, get_, create_, draft_create, read) but some tools conflate multiple concerns (drive_create handles both creation and content conversion).

Tools (8)

drive_createwriteauthsource verified68/100

Crée un fichier Drive sous parent_id, avec son contenu si `content` est fourni : le texte (markdown par défaut) est converti en Google Doc rédigé — sans `content`, le fichier est créé vide. Renvoie le propriétaire (`owner`, `owned_by_me`) pour vérifier le dépôt. Soumis aux zones (policy + grants) ; si refusé : appeler access_request kind=session_grant (ou kind=grant legacy poste entier).

drive_getread onlyauthsource verified77/100

Métadonnées d'un fichier Drive par file_id (lecture), propriétaire compris : `owner` (email) et `owned_by_me` (null = non renseigné par Drive, cas des Drive partagés).

drive_listread onlyauthsource verified78/100

Liste des fichiers Drive (lecture). Filtre optionnel parent / query. Renvoie `ownership` : le propriétaire de chaque fichier (owner, owned_by_me) — pour vérifier qu'un livrable est bien sur le bon compte.

drive_readread onlyauthsource verified77/100

Lit le CONTENU d'un fichier Drive en texte (lecture, sous verrou comme drive_get). Fichier Google : export texte — markdown par défaut pour un Doc, CSV pour un Sheet. Fichier ordinaire : renvoyé tel quel s'il est textuel ; les binaires (PDF, images) ne sont pas lisibles ici. Sert à relire un document déposé ou un modèle avant de le copier.

gmail_draft_createwriteauthsource verified77/100

Issues (5)

CRITICALsecret-injection ↗

Session tokens exposed as required parameters instead of server-side injection. All 8 tools require 'session' parameter, violating secret-injection pattern. Tokens appear in logs, traces, and LLM context.

profiles_listgmail_listgmail_getgmail_draft_createdrive_listdrive_getdrive_createdrive_read

HIGHtool-annotations ↗

No tool annotations (readOnlyHint/destructiveHint/idempotentHint) despite clear risk levels. Tools marked READ_ONLY and WRITE in metadata but not exposed to LLM via schema annotations.

gmail_draft_createdrive_create

HIGHresponse-shaper ↗

Output schemas not documented. LLMs cannot predict response structure for 'ownership', 'owner', 'owned_by_me' fields or pagination behavior. Breaks tool-chaining pattern.

profiles_listgmail_listgmail_getdrive_listdrive_getdrive_create

Recommendations

Move session tokens to server-side injection via environment or request headers. Remove 'session' parameter from all tools. Implement per-request _meta.sessionId or Bearer token in MCP protocol layer.
Add tool annotations to schema: readOnlyHint=true for list/get/read tools; destructiveHint=true for create/draft_create; idempotentHint=true for read-only operations. Enables LLM to reason about side effects.
Document output schemas for each tool. Example: 'Returns {profiles: [{alias, status, services}], total}' for profiles_list. Include field types and meanings so LLM can chain calls.
Refactor drive_create into two tools: (1) create_file(alias, name, parent_id, mime_type, session) → {file_id, owner, owned_by_me}; (2) convert_and_upload_content(alias, file_id, content, content_type, session) → {success, file_id}. Separates concerns and enables reuse.
Shorten descriptions to 50-150 chars. Example: 'gmail_list: List unread/filtered Gmail messages. Requires session token.' instead of current 150+ char description. Use parameter descriptions for details.

Score history

Overall score trend

First recorded score · v2 rubric

56/100

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