Microsoft Outlook MCP server with built-in OAuth onboarding for mail, calendar, and contacts
20 tools with consistent verb-noun naming (list_, read_, send_, create_, update_, delete_, get_). All tools have descriptions (avg ~80 chars, baseline 194). Input schemas present for all tools with type definitions and required fields. However, parameter descriptions are MISSING, the schema shows properties but no 'description' field for individual params. Output schemas are undocumented. Error handling is minimal; no recovery guidance or actionable error messages visible in code. Destructive operations (delete_draft, delete_calendar_event, delete_contact) require confirm+reason but lack dry-run alternatives. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Composition is sound, tools chain well (e.g., list_accounts → read_emails → get_email_thread). Naming is clear and action-oriented.
Start OAuth onboarding for an Outlook account using Microsoft app credentials.
Create a calendar event in an Outlook account.
Create a contact in an Outlook account.
Create an Outlook draft message.
Delete a calendar event from an Outlook account.
Delete a contact from an Outlook account.
Delete an Outlook draft message by message_id.
Parameter descriptions missing from all 20 tools. Schema defines properties (account, to, subject, etc.) but no 'description' field for each param. LLMs cannot infer parameter meaning from names alone (e.g., 'html' could mean output format or email body format).
Output schemas undocumented. No visible documentation of what fields read_emails, get_email_thread, list_calendar_events, or list_contacts return. LLMs cannot plan downstream tool calls or extract required IDs without knowing response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Complete OAuth onboarding using either the auth code or the full redirected URL.
Get all attachments from an email.
Get a single attachment from an email by attachment_id.
Get an Outlook conversation thread by conversation_id or by starting from a message_id.
List all configured Outlook accounts and their authentication/health status.
List calendar events for an account within a date range.
List contacts from an Outlook account.
List Outlook mail folders for an account.
Read recent Outlook emails from one account or aggregate across all enabled accounts when account is omitted.
Send an email from an Outlook account.
Update a calendar event in an Outlook account.
Update a contact in an Outlook account.
Update an Outlook draft message by message_id.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Destructive tools (delete_draft, delete_calendar_event, delete_contact) lack explicit destructiveHint. Read-only tools lack readOnlyHint. Agents cannot distinguish safe from unsafe operations without parsing descriptions.
Destructive operations require confirm=true + reason but lack dry-run or preview. Agents cannot preview consequences before committing. No recovery tools (e.g., restore_draft, restore_contact) if deletion is accidental.
Error handling minimal. Code shows requireConfirm() and requireString() validators but no visible error recovery guidance. Errors like 'Missing or invalid account' do not suggest next steps (e.g., 'Call list_accounts() to see available accounts').