Loading ToolBench

Reading the current corpus…

mcp-server-outlook MCP server · F · ToolBench

mcp-server-outlook

MCP server for automating Microsoft Outlook via COM interop. Provides tools for mailboxes, folders, mail items, drafts, attachments, calendar, and contacts from AI assistants and coding agents.

<=2025-11-25STDIO1 tools

35/100

Definition Quality27

Protocol Readiness47

Supportability41

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Single tool 'application' with verbose description (250+ chars) but critical schema gaps. Input schema visible with enum action parameter and boolean includeActiveContext, but output schema completely undocumented. No parameter descriptions provided for either input field. Tool name 'application' is generic and does not follow verb_noun pattern (should be 'get_outlook_status' or similar). No error handling guidance. Tool definition inferred from test file rather than explicit registration in source.

Tools (1)

applicationread onlysource verified27/100

Inspect the current Outlook desktop application state without opening a persistent session. Use get-status to verify Outlook availability, inspect active explorer/inspector counts, and read the current folder context. Use get-active-explorer to find out which folder the user is looking at and what is selected there, and get-active-inspector to find out which item the user currently has open. Both answer "nothing is open" as a success rather than an error. An item the user is still composing has not been saved and therefore has no entryId, so it cannot be addressed by any other action until it is saved; isSaved says which case you are in.

Issues (5)

HIGHtool-naming ↗

Tool name 'application' is generic and does not start with action verb. Should be 'get_outlook_status', 'inspect_outlook', or similar to clarify intent.

application

CRITICALtool-description ↗

Input parameters 'action' and 'includeActiveContext' lack descriptions. LLMs cannot infer what 'includeActiveContext' controls or when to set it.

application

CRITICALresponse-shaper ↗

Output schema completely undocumented. Tool description mentions returning status, explorer, and inspector info, but no structured output schema is defined. LLMs cannot plan downstream calls without knowing response fields.

application

HIGHtool-registration ↗

Tool definition inferred from test file (McpServerIntegrationTests.cs) rather than visible in explicit tool registration code. Cannot verify actual schema implementation.

application

Recommendations

Rename tool from 'application' to 'get_outlook_status' or 'inspect_outlook_state' to follow verb_noun pattern and clarify action.
Add descriptions to both input parameters: 'action' should explain the three enum options (get-status, get-active-explorer, get-active-inspector); 'includeActiveContext' should explain what context data is included when true.
Document the output schema with typed fields for each action: e.g., for get-status return {isAvailable: bool, activeExplorerCount: int, activeInspectorCount: int}; for get-active-explorer return {folderName: string, selectedItemCount: int, ...}.
Move tool definition from test file to explicit registration in McpServer code with full schema and descriptions visible in source.
Add error handling guidance: 'If Outlook is not running, returns isAvailable: false. If COM access fails, returns error with recovery hint to check Outlook permissions.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

35/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	35	<=2025-11-25	v2