Loading ToolBench
Unified inbox MCP server for multiple Gmail accounts with HTML/Markdown support and attachments
Solid tool definitions with complete schemas and descriptions for all 11 tools. Naming follows verb_noun convention consistently (add_account, list_accounts, get_messages, search, archive_message, send, reply). All tools have non-empty descriptions (avg ~120 chars, within 10-1024 baseline). Input schemas are present with typed properties and required arrays. However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Parameter descriptions are adequate but lack format constraints (e.g., maxResults has no min/max bounds). Error handling and recovery guidance are absent from descriptions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE, REVERSIBLE). Missing dependency hints (e.g., 'Call add_account first') and no guidance on when to use similar tools (get_messages vs search). Composition is good, tools are single-responsibility and chainable (e.g., search returns messageId, get_message accepts messageId). Security concern: OAuth tokens stored in better-sqlite3 without visible encryption or secret injection pattern.
Add a new Gmail account to the unified inbox. Opens a browser window for OAuth authentication.
Archive a single message (removes it from inbox but keeps it in the account).
Archive multiple messages at once (removes them from inbox but keeps them in the account).
Get details of a specific message, optionally including the full body content.
Get a unified stream of messages from all connected accounts, sorted by date (newest first).
List all connected Gmail accounts with their unread counts and connection status.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination) for downstream tool chaining. E.g., does get_messages return messageId, threadId, and account for chaining to get_message? Unknown.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels declared (READ_ONLY, WRITE, DESTRUCTIVE, REVERSIBLE). Agents cannot distinguish safe retry behavior.
Numeric parameters lack bounds. maxResults has no min/max (default 50 for get_messages, 20 for search, inconsistent). LLMs may pass absurd values (0, 999999) causing API errors or timeouts.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Remove a Gmail account from the unified inbox.
Reply to a specific message. Supports plain text, HTML, or markdown formatting, plus attachments.
Search for messages across all connected accounts using Gmail search syntax.
Send an email from a specific account. Supports plain text, HTML, or markdown formatting, plus attachments.
Get a summary of all connected accounts including unread counts and recent message subjects.
No error recovery guidance in descriptions. E.g., remove_account has no hint about what happens if the account is not found or if removal fails. Agents cannot self-correct.
OAuth tokens stored in better-sqlite3 without visible encryption. Token Store class (auth/token-store.js) not shown, cannot verify if secrets are encrypted at rest or if server-side secret injection is used.