MCP server for Claude to access Outlook data via Microsoft Graph API
18 tools with complete input schemas and descriptions, but quality is uneven. Naming follows verb_noun convention (list-events, send-email, create-rule). Descriptions are present but often generic (avg ~80 chars, below 194-char baseline). Parameters lack depth: no enums for constrained values (e.g., folder names, importance levels), no min/max bounds, no format guidance. Output schemas are undocumented, LLMs cannot predict response structure. Error handling is absent from visible code. Security concerns: no evidence of permission gates, audit logging, or secret injection patterns. Composition is reasonable (18 focused tools), but missing idempotency guarantees and pagination details.
Returns information about this Outlook Assistant server
Authenticate with Microsoft Graph API to access Outlook data
Cancels a calendar event
Check the current authentication status with Microsoft Graph API
Creates a new calendar event
Creates a new mail folder
Creates a new inbox rule
No output schemas documented. LLMs cannot predict response structure, forcing them to guess at field names and types for downstream tool chaining.
Constrained parameters lack enums. 'folder' in list-emails accepts free-form strings (inbox, sent, drafts) but no enum constraint; 'importance' in send-email has enum but others don't. LLMs will hallucinate invalid folder names.
Numeric parameters lack bounds. 'count' in list-events and list-emails (max 50) and 'sequence' in edit-rule-sequence have no min/max constraints in schema. LLMs may pass 0, negative, or absurdly large values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Declines a calendar event
Deletes a calendar event
Changes the execution order of an existing inbox rule
Lists recent emails from your inbox
Lists upcoming events from your calendar
Lists mail folders in your Outlook account
Lists inbox rules in your Outlook account
Moves emails from one folder to another
Reads the content of a specific email
Search for emails using various criteria
Composes and sends a new email
No error handling guidance. Code shows no try-catch blocks, no error classification (retryable vs fatal), no recovery hints. If a tool fails, LLMs have no guidance on what to do next.
No idempotency guarantees. Destructive tools (delete-event, send-email) do not declare idempotency. Agents retrying on ambiguous failures risk duplicate sends or deletes.