Multi-account Outlook MCP server with JIT account switching for Claude Code.
Server has 16 well-named tools with consistent verb_noun patterns (outlook_list_*, outlook_search_*, outlook_send_*, etc.). All tools have descriptions and input schemas are present with types. However, descriptions are often generic (e.g., 'List all configured Outlook accounts') and lack actionable context for LLM selection. Parameter descriptions are present but minimal, many lack format/constraint details. Output schemas are not documented; responses are JSON strings without field-level documentation. Error handling returns JSON with 'error' key but lacks recovery guidance or categorization. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Batch tools (outlook_batch_delete_emails, outlook_batch_modify_emails, outlook_batch_move_emails) are good composition patterns but lack per-item success/failure reporting.
Move multiple email messages to Deleted Items in batches.
Modify properties on multiple messages in batches (read status, categories, flags).
Move multiple email messages to a specific folder in batches.
Show the currently active Outlook account name and email.
Move an email message to Deleted Items.
Download an email attachment by message ID and attachment ID.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels declared in metadata. Tools like outlook_delete_email and outlook_batch_delete_emails are DESTRUCTIVE but lack destructiveHint annotation to warn agents.
Output schemas not documented. Tools return JSON strings but field structure, types, and required fields are not declared. LLMs cannot plan downstream calls or extract data reliably without knowing response schema.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Create a draft email message without sending it.
List messages in a specific folder.
List all mail folders for the account.
List all configured Outlook accounts and which one is currently active.
Update properties on a single message (read status, categories, flags).
Move an email message to a specific folder.
Read a full email message including body, headers, and attachment metadata.
Search emails using Outlook search syntax. Searches ALL accounts when no account is specified.
Send an email via Microsoft Graph. Supports plain text, HTML, CC/BCC, and replies.
Switch the active Outlook account. All subsequent operations will use this account by default.
Descriptions lack actionable context. Most are under 100 chars and do not explain WHEN to use the tool vs similar ones, or what the LLM should expect. E.g., 'List all configured Outlook accounts' does not hint that this is a discovery tool to call before switching accounts.
Error handling returns generic JSON with 'error' key but does not categorize errors (retryable vs user-fixable vs fatal) or provide recovery guidance. E.g., 'Account not found' should suggest 'Call outlook_list_accounts to see available accounts.'
Batch tools (outlook_batch_delete_emails, outlook_batch_modify_emails, outlook_batch_move_emails) lack per-item success/failure reporting. If 1 of 50 messages fails, the response does not indicate which one or why, forcing the agent to retry all 50.